Skip to content
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.

Sign up for GitHub

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

Jump to bottom

find::matchers::printf::tests::test_printf_special_types fails from time to time #177

Closed
sylvestre opened this issue Aug 10, 2022 · 2 comments
Closed

find::matchers::printf::tests::test_printf_special_types fails from time to time #177

sylvestre opened this issue Aug 10, 2022 · 2 comments

Comments

@sylvestre
Copy link
Contributor 


---- find::matchers::printf::tests::test_printf_special_types stdout ----
thread 'find::matchers::printf::tests::test_printf_special_types' panicked at 'Couldn't find fifo in /tmp/exampleZwqMxS', src/find/matchers/mod.rs:569:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

example: https://github.com/uutils/findutils/runs/7684599223?check_suite_focus=true

@refi64 rings a bell ?
refi64 added a commit to refi64/findutils that referenced this issue Aug 12, 2022
@refi64
find: Don't swallow mkfifo errors in the tests
07916e1 
Use nix's version of mkfifo instead, which lets us easily access the
errors and then fail with more information than the FIFO mysteriously
not appearing.

Ref. uutils#177.

Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>
@refi64 refi64 mentioned this issue Aug 12, 2022
Merged
@refi64
Copy link
Contributor

refi64 commented Aug 12, 2022

Hmm...my best guess is that the FIFO never gets created, so I opened #179 to fail more explicitly in that case. I'm not sure what would cause that to happen though...

@sylvestre
Copy link
Contributor Author

seems much better :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sylvestre @refi64