SpinResearch / RustySecrets / 195

69%

Build Type

push

travis-ci

Committed by Romain Ruetschi

Commit Message

<a href="https://github.com/SpinResearch/RustySecrets/commit/<a class=hub.com/SpinResearch/RustySecrets/commit/12cefb1d18ed0ccd8059e4b993ea66a959a40c10">12cefb1d1<a href="https://github.com/SpinResearch/RustySecrets/commit/12cefb1d18ed0ccd8059e4b993ea66a959a40c10">&quot;&gt;Rustfmt updates + refactor Travis configuration (#60)

* Update rustfmt compliance

Looks like rustfmt has made some improvements recently, so wanted to bring the
code up to date.

* Add rustfmt to nightly item in Travis matrix

* Use Travis Cargo cache

* Allow fast_finish in Travis

Items that match the `allow_failures` predicate (right now, just Rust nightly),
will still finish, but Travis won&amp;#39;t wait for them to report a result if the
other builds have already finished.

* Run kcov in a separate matrix build in Travis

* Rework allowed_failures logic

We don&amp;#39;t want rustfmt to match `allow_failures` just because it needs to use
nightly, while we do want nightly to match `allow_failures`. Env vars provide a
solution.

* Add --all switch to rustfmt Travis

* Test building docs in Travis

* Use exact Ubuntu dependencies listed for kcov

Some of the dependencies we were installing were not listed on
https://github.com/SimonKagstrom/kcov/blob/master/INSTALL.md, and we were
missing one dependency that was listed there. When `sudo: true` Travis uses
Ubuntu Trusty.

* No need to build before running kcov

kcov builds its own test executables.

* Generate `Cargo.lock` w/ `cargo update` before running kcov

As noted in </a><a class="double-link" href="https://github.com/SpinResearch/RustySecrets/commit/<a class="double-link" href="https://github.com/SpinResearch/RustySecrets/commit/aeb3906cce8e3e26c7bc80d6aec417b365f3d2f1">aeb3906cc</a>">aeb3906cc</a><a href="https://github.com/SpinResearch/RustySecrets/commit/12cefb1d18ed0ccd8059e4b993ea66a959a40c10"> it is not necessary to
build the project before running kcov, but kcov does require a `Cargo.lock`
file, which can be generated with `cargo update`.

Run Details

1 of 1 new or added line in 1 file covered. (100.0%)

955 of 1363 relevant lines covered (70.07%)

0.7 hits per line