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.

Sign up for GitHub

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

Jump to bottom

Random test failures #710

Closed
paul-rouse opened this issue Sep 22, 2017 · 1 comment
Closed

Random test failures #710

paul-rouse opened this issue Sep 22, 2017 · 1 comment

Comments

@paul-rouse
Copy link
Contributor

We have been having a lot of trouble with random test failures on Travis, many of which are caused by the 10-minute timeout when no output is produced. This seems to have become frequent over the last three months, and may be related to similar problems encountered by other people: travis-ci/travis-ci#8162, travis-ci/travis-ci#8165 and flux-framework/flux-core#1141.

Following the hints, especially in the last of those links, I have put in PR #709 which changes the Travis environment to a VM instead of a container. Since it's a one-liner affecting only the test configuration, I'll merge it as soon I am sure the tests pass.

However, I'll leave this issue here for a few days because there is something slightly worrying about needing to do this. The failures all seem to occur when compiling the actual test modules: usually the last line reported is Compiling PersistentTest.hs. Could it be something to do with memory usage (the VMs have more than the containers)?
@paul-rouse paul-rouse mentioned this issue Sep 22, 2017
Merged
@paul-rouse
Copy link
Contributor Author

Let's close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@paul-rouse