Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upShrink test output in CI #83
Conversation
|
Here's an example build with a failing test: https://travis-ci.org/servo/html5ever/builds/49209191 And an example build with all passing (or ignored) tests: https://travis-ci.org/servo/html5ever/builds/49209313 |
|
Nice trick :) Can you move the output condenser script to |
|
OK, I moved it to a separate Python script. |
aroben
force-pushed the
aroben:shorter-ci-output
branch
2 times, most recently
from
67dfa69
to
736103c
|
Uh oh, the build "succeeded" even though compiling failed. Guess we need to get the exit status of |
Travis CI won't display build logs longer than 10,000 lines. Since we have so many tests, our CI logs get truncated and you can't see the test failures down at the end of the log. Instead of printing each test on its own line, we now just print out a single character for each test indiciating success (.), failure (F), or that the test was ignored (I). Failing tests are still printed in full at the end of the test run.
Piping `make`'s output through `shrink-test-output.py` was swallowing `make`'s exit code. Now we explicitly use its exit code for the overall result of the build.
|
The exit code issue is fixed. Let me know what you think. Maybe this is too much complexity for the benefit? |
|
Looks great, thanks :) |
aroben commentedFeb 2, 2015
Travis CI won't display build logs longer than 10,000 lines. Since we have so many tests, our CI logs get truncated and you can't see the test failures down at the end of the log.
Instead of printing each test on its own line, we now just print out a single character for each test indiciating success (
.), failure (F), or that the test was ignored (I). Failing tests are still printed in full at the end of the test run.