-
Notifications
You must be signed in to change notification settings - Fork 138
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
Failing test #537
Failing test #537
Conversation
This new test fails, but it should succeed.
Strange, the tests seem to work on my machine, and your PR fails in CI. Do you know what the expected behavior should be, e.g. do we need to change the code? |
The expected behaviour is that the test does not fail. |
Ah, understood now, thank you. |
Fixed by #536, thank you! |
I rebased this test on the main branch. It is still failing:
|
Ah strange, I tested on my machine and it seemed to be working. Will take another look. |
Can this be reopened? |
I'm getting a github error and can't reopen it. Can you move this to a new branch? I think it might make sense to either keep the failing test code in an issue, or submit a PR with a patch. Otherwise we'll have the PR open until someone comes around to fixing it and I'd eventually like to get to 0 PRs. |
Did you got eventually this test failing on your system? Can you create some mechanism for tests, which are not supposed to fail, but currently fail (expected failures)? |
Have not tried, sorry. I have some vacation this week and can take a look. I had also thought about an expected failure system, I didn't see an obvious way when I skimmed last time. |
This new test fails, but it should succeed.