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

Make Travis tests slightly more robust by re-running them. #445

Merged
merged 1 commit into from
Jan 19, 2017

Conversation

iphydf
Copy link
Member

@iphydf iphydf commented Jan 19, 2017

This change is Reviewable

@iphydf iphydf added this to the v0.1.6 milestone Jan 19, 2017
@iphydf iphydf unassigned cebe Jan 19, 2017
@iphydf iphydf modified the milestones: v0.1.5, v0.1.6 Jan 19, 2017
@iphydf
Copy link
Member Author

iphydf commented Jan 19, 2017

Recently, tests have been timing out more often. This should mitigate it a bit. It will keep rerunning failed tests until travis times out.

@robinlinden
Copy link
Member

:lgtm_strong:


Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@iphydf iphydf merged commit a74ab7c into TokTok:master Jan 19, 2017
# Keep running tests until they eventually succeed or Travis times out after
# 50 minutes. This cuts down on the time lost when tests fail, because we no
# longer need to manually restart the build and wait for compilation.
"$@" || TESTS "$@"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

50 minutes is a bit too much imo. Maybe make a limit here on run it 3 times and then fail? If tests are broken this will take a lot of travis capacity that could be used on building other repos.

@nurupo
Copy link
Member

nurupo commented Jan 25, 2017

Rerun tests until stars align and they pass? :)


Comments from Reviewable

@iphydf iphydf deleted the rerun-tests branch January 21, 2018 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants