Skip to content

Disable test_when_piped_input_then_no_broken_pipe by default #4005

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

Merged
merged 3 commits into from
Oct 4, 2022
Merged

Disable test_when_piped_input_then_no_broken_pipe by default #4005

merged 3 commits into from
Oct 4, 2022

Conversation

sylvestre
Copy link
Contributor

It is blocking the executions of the tests and I suspect it is breaking android

@sylvestre
Copy link
Contributor Author

Android is green again \o/

@Joining7943
Copy link
Contributor

Sorry. Yes, this test is pretty expensive and brute force. Perhaps, there is a more specific problem behind the randomness of the failures?

@sylvestre
Copy link
Contributor Author

dunno but I haven't seen it failed for a while :)

@Joining7943
Copy link
Contributor

However, nice :)

Maybe it helps. At the time of writing the test in #3910, I haven't figured out why it actually failed. The fix attached to the test just stopped it failing with tail but also with head when both tools were expected to produce no output with options like -c -0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants