Nick Mathewson authored Mar 29, 2019 and teor committed Apr 06, 2019

Diagnostic for 29241.

We need to keep the gcno files, because they are created at compile time.

When classifying a client's selection of TLS ciphers, if the client
ciphers are not yet available, do not cache the result. Previously,
we had cached the unavailability of the cipher list and never looked
again, which in turn led us to assume that the client only supported
the ancient V1 link protocol.  This, in turn, was causing Stem
integration tests to stall in some cases.  Fixes bug 30021; bugfix
on 0.2.4.8-alpha.

(Travis terminates the job after 10 minutes of no output.)

Diagnostic for 29437.

Fixes bug 30011; bugfix on 0.3.5.4-alpha.

Merge the moved coverage line from 29036 with the stem changes in
maint-0.3.5.

And add some useful comments

rl1987 authored Mar 31, 2019 and teor committed Apr 01, 2019

Also, refrain from caching target/.

See: https://levans.fr/rust_travis_cache.html

And fix a comment.

See:
https://gcc.gnu.org/onlinedocs/gcc/Gcov-Data-Files.html#Gcov-Data-Files

Otherwise, "make check-changes" will complain when we backport the change.

We need a recent test-network.sh to use new chutney features in CI.

Fixes bug 29703; bugfix on 0.2.9.1-alpha.

Part of 29806.

Copy and paste the vote=0 code from the old src/or/dirserv.c
to the new src/feature/dirauth/bwauth.c.

juga authored Mar 19, 2019 and teor committed Mar 21, 2019

so that the relays that would be "excluded" from the bandwidth
file because of something failed can be included to diagnose what
failed, without still including these relays in the bandwidth
authorities vote.

Closes #29806.

Since we have moved coveralls to the script target the entire build will
now fail if coveralls fail. We handle it more gracefully by echo'ing the
failure instead of doing a hard-failure.

See: https://bugs.torproject.org/29036

This should ensure that GCDA files are never entering the cache of
Travis CI.

See: https://bugs.torproject.org/29036