cloudmarker / cloudmarker / 223 / 1

76%

master: 84%

push

travis-ci-com

<a href="https://github.com/cloudmarker/cloudmarker/commit/<a class=hub.com/cloudmarker/cloudmarker/commit/dbd3e9fcc349a98eca1aab4864507313ab53676f">dbd3e9fcc<a href="https://github.com/cloudmarker/cloudmarker/commit/dbd3e9fcc349a98eca1aab4864507313ab53676f">&quot;&gt;Do not run &amp;#39;clean&amp;#39; target before running &amp;#39;lint&amp;#39;

This change fixes an issue introduced in commit
</a><a class="double-link" href="https://github.com/cloudmarker/cloudmarker/commit/<a class="double-link" href="https://github.com/cloudmarker/cloudmarker/commit/1ee640a60173e06841e19058a9cea10d34db2a07">1ee640a60</a>">1ee640a60</a><a href="https://github.com/cloudmarker/cloudmarker/commit/dbd3e9fcc349a98eca1aab4864507313ab53676f"> which we will call as the
*faulty commit*. The faulty commit made the `lint` target depend on the
`clean` target, so that the `clean` target is run before the `lint`
target. That change was done so that `build/*` files (created by the
invocation of `setup` module in `cloudmarker/test/test_setup.py`) were
removed before the linters are run, otherwise the linters would detect
problems in the `build` directory too.

While the faulty commit solved the problem described in the previous
paragraph, it also introduced a new issue in Travis CI environment.
Travis CI configuration in `.travis.yml` shows that after `make checks`
is run, the `coveralls` command is run which uploads the test coverage
results to Coveralls ( https://coveralls.io/ ). But when the `coveralls`
command runs, the test coverage results no longer exist. The `checks`
target invokes `lint` as a dependency which in turn invokes `clean` as a
dependency and the `clean` target removes the test coverage results.

Due to this issue, no coverage results are available in Coveralls ever
since that change was done. See https://coveralls.io/repos/242255/builds
to confirm that there is no coverage data after build 104.

This change resolves this issue by undoing the change in that commit.
Further, to resolve the original issue of preventing the linters from
reporting errors in `build/*` directory, Pylama and isort are being
invoked with `skip` and `--skip-glob` options, respectively, to skip
files in the `build` directory.

64 of 97 branches covered (65.98%)

Branch coverage included in aggregate %.

380 of 486 relevant lines covered (78.19%)

0.78 hits per line