-
Notifications
You must be signed in to change notification settings - Fork 27
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
Tests don't run to completion on macOS #269
Comments
That's interesting, I personally work on macOS as well and "it works on my machine" 😄 Can you tell me a bit more about how you've tried to run the tests.
You've run into the safety mechanism in the test setup script that makes sure it's not run multiple times simultaneously. It does so using a lock file in your tmp folder. It seems that file exists on your machine. Generally, the cleanup should delete the associated lock file, but it might have failed somehow. Perhaps due to permissions. You could try deleting the file yourself: |
Since tests can be run simultaneously, and this script exits with a success error code, isn't a race condition possible?
I set I used Process Monitor to see that the setup script was only executed once, and the cleanup script was only executed once, during the entire test run (the other attempts that are throwing ENONET just... not happening). This is so strange 🙃 |
On macOS, some acceptance tests fail with the following:
However, others execute the setup script just fine, which Objective-See's Process Monitor shows.
When setting
shell
totrue
and piping the stdout and stderr of the setup script, I at least saw these:Wouldn't this then cause the subsequent test to fail, since the repo may or may not be created at this point?
This is a very strange issue that I can't reproduce on Linux, and may be an
execa
bug...?The text was updated successfully, but these errors were encountered: