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

Travis test failures #272

Closed
flovilmart opened this issue Feb 5, 2016 · 8 comments
Closed

Travis test failures #272

flovilmart opened this issue Feb 5, 2016 · 8 comments

Comments

@flovilmart
Copy link
Contributor

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

@gnz00
Copy link

gnz00 commented Feb 5, 2016

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/

@gfosco
Copy link
Contributor

gfosco commented Feb 7, 2016

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.

@gfosco gfosco changed the title Tests are failing for no good reason Travis test failures Feb 7, 2016
@nlutsenko
Copy link
Contributor

Yup, I am looking into mongorunner module, looks like sometimes it just hangs indefinitely.
Couldn't reproduce locally at all, but I guess we can at least wrap it in a retry logic?

@imlucas
Copy link

imlucas commented Feb 7, 2016

👋 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

@nlutsenko
Copy link
Contributor

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.

@imlucas
Copy link

imlucas commented Mar 3, 2016

@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
Copy link
Contributor Author

@imlucas
Copy link

imlucas commented Mar 3, 2016

@flovilmart oh bummer. knew it was too good to be true...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants