-
Notifications
You must be signed in to change notification settings - Fork 189
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
Testsuite fails intermittently #368
Comments
I have not been able to reproduced this myself. The problem might still exist, but there's not much I can do about it without more information. If you have any logs from a failed run, please add them here. Otherwise I will have to close this without action |
For example, I got this error:
|
Another error:
|
Thank you. This provide some additional clues. It looks like your tests are trying to run the actual commands, rather than the mock commands from https://github.com/olofk/edalize/tree/main/tests/mock_commands which are supposed to override the ordinary binaries. |
0.5.3 has the similar failuses, see the log. It appears that many failures are due to formatting differencres. gmake is the executable for GNU Make on BSDs. We apply these patches in the port:
Ideally |
I'm also very confused about why it tries to do formatting as part of the test suite. I don't think I have seen that before. It's only supposed to run pytest. Manually running black locally, I also see a lot of errors, so we might as well just fix them. I created a freebsd branch where I have reformatted all files so that it's a bit easier to see what remaining issues we actually have. Is it possible for you to rerun the checks against that branch to see if we can get the number of errors down. There also seems to be a couple more errors and I'll try to look into those as well. And point taken about make and python3. With the new flow API, it's a bit easier to change this centrally, so I'll look into doing that once we have the other stuff taken care of. |
In most test runs many tests fail.
But every once in a while al tests succeed.
It looks like there is a dependency on the order tests are run. (PyTest runs them in parallel.)
The text was updated successfully, but these errors were encountered: