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

No longer use `travis_wait` in CI #8212

Merged
merged 1 commit into from Aug 27, 2019

Conversation

@Eric-Arellano
Copy link
Contributor

commented Aug 27, 2019

Now that we remote 99% of unit tests, travis_wait is unnecessary. CI never takes more than 20 minutes collectively. We only needed it before due to the lack of caching when using V2 locally and low levels of parallelism.

@Eric-Arellano Eric-Arellano requested a review from blorente Aug 27, 2019

@Eric-Arellano Eric-Arellano changed the title No longer use travis_wait in CI No longer use `travis_wait` in CI Aug 27, 2019

@blorente blorente merged commit b2db69a into pantsbuild:master Aug 27, 2019

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@stuhood

This comment has been minimized.

Copy link
Member

commented Aug 29, 2019

Unfortunately I just saw a timeout for the unit test shard on #8221.

From the log entry timestamps, it feels like we might be buffering our output rather than actually flushing it in a timely manner? Because the timestamps look like they should be sufficient to avoid an issue here.

@Eric-Arellano Eric-Arellano deleted the Eric-Arellano:no-more-travis-wait branch Aug 31, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.