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.

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: f2361_sort_nested_files #2794

Open
oconnor663 opened this issue Apr 30, 2024 · 1 comment
Open

failing test: f2361_sort_nested_files #2794

oconnor663 opened this issue Apr 30, 2024 · 1 comment

Comments

@oconnor663
Copy link
Contributor

oconnor663 commented Apr 30, 2024

What version of ripgrep are you using?

master (bb8601b)

What operating system are you using ripgrep on?

CentOS Stream 9, with an XFS root filesystem

Describe your bug.

This doesn't repro every time, maybe 1/5 or 1/10.

$ git clone https://github.com/BurntSushi/ripgrep
...
$ cd ripgrep
$ cargo test f2361_sort_nested_files
...
test feature::f2361_sort_nested_files ... FAILED

failures:

---- feature::f2361_sort_nested_files stdout ----
thread 'feature::f2361_sort_nested_files' panicked at tests/feature.rs:952:5:

printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
foo
dir/bar

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
dir/bar
foo

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    feature::f2361_sort_nested_files
@sukhmel
Copy link

sukhmel commented Aug 12, 2024

Same here when building on MacOS with Nix, ripgrep version 14.1.0

error: test failed, to rerun pass --test integration
error: builder for '/nix/store/k6djbylmb9fdz4ss0dxszyx8qr9bhmcd-ripgrep-14.1.0.drv' failed with exit code 101

thread 'feature::f2361_sort_nested_files' panicked at tests/feature.rs:960:5

output is otherwise same. The second attempt was successful, so maybe a flaky test?

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

No branches or pull requests

2 participants