-
Notifications
You must be signed in to change notification settings - Fork 77
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
handle error based on exit code #2 #77
Conversation
2e7663f
to
dcc2b6a
Compare
@AlexZeitler I've tried to find what is wrong with that It seems it's unable to switch working directory properly. You can see it in output in the last run for this PR. I'm leaving output set to true in that test until it's resolved. On a side note, it might be worth it to stop rejecting when any message comes from stderr. It's probably not how we want it to behave and always wait for Also, I'll try to force git to respect |
f2a6738
to
dfd44ce
Compare
@AlexZeitler apparently CircleCI docker executor is incapable of mounting volumes to docker containers. I'm wondering how the tests worked previously with those mounts? Since the related test is basically failing due to inability to mount a directory, I'll remove the need for mounting and check a system file instead. Is that ok? |
@Steveb-p ok |
I'm pushing an updated tests then and see if it works. Please DO NOT merge it, I'll rebase and squash all those commits into one. |
Always `down` containers after test Fix workdir test failing on CircleCI See: https://support.circleci.com/hc/en-us/articles/360007324514-How-can-I-mount-volumes-to-docker-containers-
cd10088
to
5cc5ced
Compare
@AlexZeitler done. It should now properly pass all tests and should be ready for merging. |
@Steveb-p Great job, thanks! 👌 |
Fixes tests related to #75 change and includes the original commit. Rebased due to conflict with release in package-lock.json.
Changes:
close
event now properly rejects on exit code other than 0 (BREAKING CHANGE)options
argument (falls back to empty object)