-
Notifications
You must be signed in to change notification settings - Fork 13
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
hangs on failing test #38
Comments
A timeout is unlikely to be a good solution. It would be more interesting to find out why your test is hanging. |
What testing harness are you using? Maybe it doesn't handle exit codes correctly. |
What command is used to run the tests? |
npm test ~ mocha test/app.js |
This looks pretty much in line with what we use ourselves. So I don't see any major issues here. However, not that Strider already runs Please set the |
OK so here is the log. There is a UnhandledPromiseRejectionWarning somewhere...
Note the time of the previous test. The later test failed within 30 seconds... |
So I'm seeing the A clear red flag is that you seem to be running Strider on Windows. I am not aware of anyone successfully running Strider on Windows. I myself have invested quite some effort simply getting Strider to run at all on Windows for development purposes. One of the main issues with Strider/Node/npm on Windows are the hooks and scripts. When you declare a That being said, as long as there is any chance that this is a Windows-related problem, nobody is likely to look into it as Windows is not really a supported platform to run Strider on. I would recommend to run Strider on a Linux system or in Docker if the former is not available. |
nope! The |
Hmm, good point. Although I still feel like there was some issue with Either way, two of the most prominent issues with Strider on Windows were the SSH/PK integration through gitane and the use of |
I think you are referring to the |
Waht &-issue!? On windows
Maybe strider is using a bash shell, which is available on path... |
It seems that a failing test is no recognized (exit code problem!?) causing the job progress to freeze, blocking/breaking the job queue. How about a timeout hot fix? node 6.9.1 npm 3.10.8 windows 10 64bit latest strider + available updates
The text was updated successfully, but these errors were encountered: