-
Notifications
You must be signed in to change notification settings - Fork 15
Stall after downloading mongodb version #51
Comments
@flovilmart sorry to keep you waiting on this. I've definitely run into this before as have some other folks but haven't been able to properly repro :/ Retrying the job on travis then passes every time... Mind enabling debug output to see if that gets us any more info? I've done the same over here and will continue clicking retry until it fails |
@imlucas I'll definitely try. |
https://s3.amazonaws.com/archive.travis-ci.org/jobs/107316511/log.txt Here's the log that we have, and we clearly see that the download don't even get any progress. A rate limit problem maybe? |
Here is the log from a stalled run: https://api.travis-ci.org/jobs/107587416/log.txt |
sorry... |
Misbehaving code: https://github.com/mongodb-js/version-manager/blob/master/lib/download.js#L25-L76 We should switch this to nugget which is what electron-prebuilt uses under the hood: https://github.com/electron-userland/electron-download/blob/master/index.js#L57-L75 |
sounds like a plan, want me to pr? |
@flovilmart that would be fantastic! |
I'll give it a shot |
Hopefully finally gets to the bottom of #51. HT @flovilmart!
Found it! https://travis-ci.org/mongodb-js/runner/jobs/119598613 There's a race in |
I had an issue where mongodb-runner would say that mongo is running while its not running, see Is this related to this issue or should I open another one?
|
Seeing a similar problem when trying to use mongodb-runner with Parse server. Runs perfectly on my Mac but someone has just reported an issue on Linux (the script stalls). Trace below:
Reported here: bakery/todomvc-react-native#3 (comment) |
We haven’t seen the issue in a while now, I believe we can safely close. Feel free to ring up here if we need to reopen. |
We're seeing a huge amount of tests failing on https://github.com/parseplatform/parse-server on random builds after the download of the mongo db.
Any idea, cue of something we'd be doing wrong.
The text was updated successfully, but these errors were encountered: