Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use quieter test output when running tests on Travis CI #36788

Closed
frewsxcv opened this issue Sep 27, 2016 · 5 comments
Closed

Use quieter test output when running tests on Travis CI #36788

frewsxcv opened this issue Sep 27, 2016 · 5 comments
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@frewsxcv
Copy link
Member

Currently on Travis CI for this repository, running the full test suite results in one having to download the raw log because the entire log is too long to fit in Travis CI's web UI. It also causes my browser tab to halt for a few seconds to render. I propose we turn on the quieter test output for test running on Travis CI. This will also make it easier to find test failures for PRs where there are failures.

@alexcrichton
Copy link
Member

Sounds like a great idea!

@frewsxcv
Copy link
Member Author

@alexcrichton Have any suggestions about how to accomplish this with rustbuild?

@alexcrichton
Copy link
Member

Perhaps could be a ./configure option which is threaded through to the tests themselves?

@sfackler sfackler added the E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue. label Sep 29, 2016
frewsxcv added a commit to frewsxcv/rust that referenced this issue Oct 30, 2016
sophiajt pushed a commit to sophiajt/rust that referenced this issue Nov 2, 2016
Use quieter test output when running tests on Travis CI.

Fixes rust-lang#36788.
@frewsxcv frewsxcv reopened this Apr 10, 2017
@frewsxcv
Copy link
Member Author

Nevermind, I guess this was intentionally turned off in 2727866

@alexcrichton
Copy link
Member

Ah yeah this was explicitly re-enabled to help diagnose flaky failures we've been having.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

3 participants