-
Notifications
You must be signed in to change notification settings - Fork 234
COMPASS-2110: Investigate timeouts on Travis #1247
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
Conversation
Aggregated and sorted alphabetically to make any patterns clearer - first failure results from these initial 40 noop runs:
[collections affected] https://travis-ci.com/10gen/compass/jobs/92374414
[data-service affected] https://travis-ci.com/10gen/compass/jobs/92372412
[explain, indexes, query-bar, schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92373939
[indexes, query-bar, schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92374312
[query-bar, schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92372411
[schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92374599
[sidebar affected] https://travis-ci.com/10gen/compass/jobs/92374595 |
Whatever is causing these test timeouts or hangs, I read as the test runner can recover from the |
Another potentially interesting data point is that |
It was not created by this test, so if it's needed it would be for earlier test runs? I don't see value in keeping it. Plus - it might be how the chain of test timeouts gets broken? Let's find out with another test.
If #databases always works, perhaps there's a race at createCollection/insertMany/insertOne? Will do another 40 jobs to get more data.
Next 44 runs results:
[connect affected] https://travis-ci.com/10gen/compass/jobs/92383744
[collections, schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92382796
[databases, explain, indexes, query-bar, schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92384608
[explain, indexes, query-bar, schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92382603
[indexes, query-bar, schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92383741
[query-bar, schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92382696
[schema, sidebar affected] https://travis-ci.com/10gen/compass/jobs/92382800
[schema affected, 5 failures] https://travis-ci.com/10gen/compass/jobs/92383616
[sidebar affected] https://travis-ci.com/10gen/compass/jobs/92384429
[sidebar affected] https://travis-ci.com/10gen/compass/jobs/92384423 |
From this data, I'm currently thinking:
|
Results from the next 44 runs (Friday evening + Tue morning AEDT): (Friday only so far)
https://travis-ci.com/10gen/compass/jobs/92580507 (Friday only so far)
https://travis-ci.com/10gen/compass/jobs/92582209 (Tuesday only so far)
https://travis-ci.com/10gen/compass/jobs/92919029 |
Plan for todayAs the
Will use any verification Travis run if I make progress on this |
They are redundant as they are already done by goToCollection, which is at least a code smell worthwhile removing.
So far this is not a solution for |
To hopefully help diagnose the underlying issue.
Well if https://travis-ci.com/10gen/compass/jobs/92927263 was the only failure in >80 jobs I think that's more than enough to call this done, follow up work to get this onto master will be in https://jira.mongodb.org/browse/COMPASS-2159 |
Checklist
DEBUG=*
?DEBUG=*
...