Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:26:32Zhttps://gitlab.torproject.org/legacy/trac/-/issues/26335Use fewer travis builders for typical commits?2020-06-13T15:26:32ZNick MathewsonUse fewer travis builders for typical commits?We have accumulated a bunch of travis build processes. Maybe some of them should be "fast" ones that happen for every commit in every branch, and some should be "slow" ones that happen for pull requests and the mainline branch?
Or ther...We have accumulated a bunch of travis build processes. Maybe some of them should be "fast" ones that happen for every commit in every branch, and some should be "slow" ones that happen for pull requests and the mainline branch?
Or there might be some even better way to make this decision.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/26334Investigate how much our CI performance would improve (if at all) with paid b...2020-06-13T15:26:32ZNick MathewsonInvestigate how much our CI performance would improve (if at all) with paid buildersTor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/25936have travis display test-suite.log from the right place when DISTCHECK=yes2020-06-13T15:24:55ZTaylor Yuhave travis display test-suite.log from the right place when DISTCHECK=yesAfter #25814, Travis CI sometimes won't find test-suite.log because `make distcheck` runs `make check` in a subdirectory. This causes problems when there's a failure that's specific to `make distcheck`, like in [this example](https://tr...After #25814, Travis CI sometimes won't find test-suite.log because `make distcheck` runs `make check` in a subdirectory. This causes problems when there's a failure that's specific to `make distcheck`, like in [this example](https://travis-ci.org/torproject/tor/jobs/371634830).
We should create a new make target that shows test-suite.log from the correct place. (It's easier if it's a make target because then we have `$(distdir)` available.)Tor: 0.3.4.x-finalTaylor YuTaylor Yuhttps://gitlab.torproject.org/legacy/trac/-/issues/25818Investigate using coveralls with travis2020-06-13T15:24:28ZNick MathewsonInvestigate using coveralls with travisCoveralls can let us know when pull requests would change test coverage, and by how much.Coveralls can let us know when pull requests would change test coverage, and by how much.Tor: 0.3.4.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/25814Should Travis use "make distcheck"?2020-06-13T15:24:27ZNick MathewsonShould Travis use "make distcheck"?I just noticed that we had broken "make dist" on master, because one of the jenkins builders wasn't passing. I fixed it with 197d1992dba2fe.
Should our Travis builds be reconfigured to use "make distcheck" instead of "make all && make ...I just noticed that we had broken "make dist" on master, because one of the jenkins builders wasn't passing. I fixed it with 197d1992dba2fe.
Should our Travis builds be reconfigured to use "make distcheck" instead of "make all && make check"? It takes only a little bit longer, but it would help us be sure that we weren't running into any issues like the one above, or #25732.
Instead of passing things to "configure" directly in this case, we would need to use the `DISTCHECK_CONFIGURE_FLAGS` flag to set the configuration options that distcheck would use.Tor: 0.3.4.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/25788Can Travis check 32-bit builds?2020-06-13T15:24:24ZNick MathewsonCan Travis check 32-bit builds?We ran into a problem recently with some bugs that only affected 32-bit builds. Fortunately, Jenkins caught them, but it would be cool if we could get Travis to check them too. Is that viable?
We don't have to necessarily build **on** ...We ran into a problem recently with some bugs that only affected 32-bit builds. Fortunately, Jenkins caught them, but it would be cool if we could get Travis to check them too. Is that viable?
We don't have to necessarily build **on** a 32-bit platform, just so long as we build somewhere where we can target 32-bit builds, and exceute them.Tor: unspecifiedhttps://gitlab.torproject.org/legacy/trac/-/issues/25714switch Travis to using Rust stable2020-06-13T15:24:09ZTaylor Yuswitch Travis to using Rust stableRight now our Travis use Rust nightly instead of stable. Now that we are standardizing on a stable Rust (see #24765), we should have Travis use stable so we catch accidental uses of nightly features.Right now our Travis use Rust nightly instead of stable. Now that we are standardizing on a stable Rust (see #24765), we should have Travis use stable so we catch accidental uses of nightly features.Tor: 0.3.4.x-finalTaylor YuTaylor Yuhttps://gitlab.torproject.org/legacy/trac/-/issues/25549Add tor CI config for AppVeyor2020-06-13T15:24:58ZIsis LovecruftAdd tor CI config for AppVeyorAt the Rome meeting, it was discussed (apparently, I wasn't there that time) to have an AppVeyor config for tor. As I understand it (and please feel free to correct this ticket!), the idea is to have multiple CI systems running (which i...At the Rome meeting, it was discussed (apparently, I wasn't there that time) to have an AppVeyor config for tor. As I understand it (and please feel free to correct this ticket!), the idea is to have multiple CI systems running (which is a thing we already do!). For example, currently, we have [Jenkins](https://jenkins.torproject.org) and we also have TravisCI for personal (Github-based) forks (as per #22636): Jenkins tests (essentially) (Debian package-based) builds on `master` and known (supported) tor versions, while Travis tests _anything any developer pushes_ (albeit only for GCC/Clang on Linux, because everything else is unsupported/slow).
We should setup an AppVeyor config for testing tor on Windows. Ideally, it should match the testing behaviour of our Jenkins/Travis builds, so that we don't get spurious errors on one system or another.Tor: 0.3.4.x-finalhttps://gitlab.torproject.org/legacy/trac/-/issues/23883document how to get Travis CI running on your fork of tor2020-06-13T15:16:00ZTaylor Yudocument how to get Travis CI running on your fork of torTor: 0.3.4.x-finalAlex XuAlex Xu