Last Friday we started experiencing strange intermittent test failures where a huge number of tests would unexpectedly pass, while the rest would time out. This affected builds throughout the weekend, and I was able to narrow down the cause to the test suite's HTTP server returning 404s for every single test file. This in turn was caused by a nightly performance testing job that failed to shut down its own HTTP server, which will be fixed by https://github.com/servo/servo/pull/19474.
This will also address any problems with the CI end-to-end times that cropped up over the weekend, which was really just a symptom of hitting the test harness timeout for every single 404 test file. We will look into whether we can run the conflicting servers in ways so they can't conflict, as well as whether a sanity check is possible to quickly report if the test server is not behaving as expected. Cheers, Josh _______________________________________________ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
