8000 Unexpected Test Failure in `test_du_no_dereference` · Issue #5585 · uutils/coreutils · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Unexpected Test Failure in test_du_no_dereference #5585

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

Closed
allaboutevemirolive opened this issue Nov 27, 2023 · 0 comments · Fixed by #5625
Closed

Unexpected Test Failure in test_du_no_dereference #5585

allaboutevemirolive opened this issue Nov 27, 2023 · 0 comments · Fixed by #5625
Labels

Comments

@allaboutevemirolive
Copy link
Contributor
allaboutevemirolive commented Nov 27, 2023

I encountered an unexpected test failure while running cargo test, specifically in the test_du::test_du_no_dereference test case. The failure seems to be related to the use of symbolic links in the /tmp directory.

Error Output:

failures:

---- test_du::test_du_no_dereference stdout ----
mkdir: /tmp/.tmpaRZr6V/a_dir
symlink: /tmp/.tmpaRZr6V/a_dir,/tmp/.tmpaRZr6V/symlink
run: /home/nemesis/Documents/Github/Focus/util/coreutils_master/target/debug/coreutils du -P
run: /home/nemesis/Documents/Github/Focus/util/coreutils_master/target/debug/coreutils du --dereference -P
run: /home/nemesis/Documents/Github/Focus/util/coreutils_master/target/debug/coreutils du -P --dereference
thread 'test_du::test_du_no_dereference' panicked at tests/by-util/test_du.rs:372:14:
'4	./a_dir
8	./subdir/deeper/deeper_dir
16	./subdir/deeper
16	./subdir/links
36	./subdir
48	.
' does not contain 'symlink'

failures:
    test_du::test_du_no_dereference

test result: FAILED. 2540 passed; 1 failed; 28 ignored; 0 measured; 0 filtered out; finished in 60.97s

error: test failed, to rerun pass `--test tests`

Steps to Reproduce:
In the project directory, run cargo test.

Additional Information:

  • The error is consistently reproduced on local machines.
  • The error does not trigger the repository CI, possibly due to differences in the filesystem (as discussed here).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0