-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Travis test failures #272
Comments
I had to close/re-open my PR to get it to trigger a rebuild twice before they passed. I believe the issue is that the timeout of 10 minutes is reached while downloading the mongodb versions. Perhaps there is a way to cache: https://docs.travis-ci.com/user/caching/ |
Yeah there is some flaky behavior, some because of mongorunner/travis. We can re-run tests selectively when this happens, you don't need to close/re-open a PR. |
Yup, I am looking into |
👋 Working on it w/ @flovilmart on mongodb-js/runner#51 (sadly, we haven't been able to sort this one out either as it's so sporadic w/ no repro). We need to fix this for you though. @Machyne: any chance you're around? could use some fresh eyes |
Looks like this is no longer a problem, since we are caching things on Travis. Closing this for now, please reopen if you see this issue again. |
@nlutsenko @flovilmart woot! thanks for hanging in there. believe this was actually resolved by some recent work on internal infrastructure that was serving the zips/tars. |
@flovilmart oh bummer. knew it was too good to be true... |
Many test builds seems to be failing because the test process don't start properly after mongoldb-runner.
I've opened a ticket on their side for investigation mongodb-js/runner#51
The text was updated successfully, but these errors were encountered: