-
Notifications
You must be signed in to change notification settings - Fork 62
Remove sporadicly failing test #99
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
Conversation
bors merge=petreeftime |
99: Remove sporadicly failing test r=petreeftime a=matthiasbeyer This is obviously not how it is done. This patch will be merged to master so that we can work on master without issues, but a PR will be filed to revert this patch immediately... with a fix, if someone can come up with one. --- This currently blocks the 0.6.0 release. I know that this is not how it is done, but I don't see a better way. Co-authored-by: Matthias Beyer <[email protected]>
Build failed: |
I think the issue might be due to some shared resource between tests. All tests execute on their own thread inside a single program and their order of execution is not guaranteed, so I think order of execution of tests or some sort of race condition might play a role in the observed bug, due to some resource which is incorrectly shared between them. |
Hm... but the tests execute subprocesses and read and write their stdin/stdout... I don't see where are shared resources, tbh. |
Line 89 in 59213cd
On the call to posix_openpt, I wonder if the |
I've tested this and it seems to pass tests on my repo. https://github.com/petreeftime/rexpect/actions/runs/4779091507 |
Let me create a PR for the fix. |
Attempted fix in #101 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This approach has my blessing. But it seems like more tests have the issue.
This is obviously not how it is done. This patch will be merged to master so that we can work on master without issues, but a PR will be filed to revert this patch immediately... with a fix, if someone can come up with one. Signed-off-by: Matthias Beyer <[email protected]>
17234ef
to
be7fb7e
Compare
Rebased to latest master, to see what's happening. |
bors try |
tryBuild failed: |
This is obviously not how it is done. This patch will be merged to master so that we can work on master without issues, but a PR will be filed to revert this patch immediately... with a fix, if someone can come up with one.
This currently blocks the 0.6.0 release. I know that this is not how it is done, but I don't see a better way.