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

par_bridge_recursion test sometimes hanging indefinitely #1142

Open
decathorpe opened this issue Mar 5, 2024 · 3 comments
Open

par_bridge_recursion test sometimes hanging indefinitely #1142

decathorpe opened this issue Mar 5, 2024 · 3 comments

Comments

@decathorpe
Copy link

decathorpe commented Mar 5, 2024

I have noticed that there is one test that sometimes just gets "stuck" and hangs indefinitely (an hour or longer, depending on how patient I am with cancelling the build):

     Running `/builddir/build/BUILD/rayon-1.9.0/target/rpm/deps/par_bridge_recursion-fe4a8a5c3a55045a`
running 1 test
test par_bridge_recursion has been running for over 60 seconds

For example, the total build time for rayon 1.9.0 was 4-5 minutes on x86_64, i686, s390x, but on ppc64le, this test has been stuck for almost two hours now.

Build environment:

  • Fedora Linux / Rawhide on ppc64le
  • Rust 1.76.0
  • distro-wide default RUSTFLAGS: -Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none
@cuviper
Copy link
Member

cuviper commented Mar 5, 2024

Maybe #1119 needs a closer look?

@decathorpe
Copy link
Author

PS: I just remembered that this might actually be not specific to ppc64le. I have seen this test hang on other architectures too, but it might just be most likely to happen on ppc64le because that is our slowest architecture and builders are often under high load.

@decathorpe decathorpe changed the title par_bridge_recursion test sometimes hanging indefinitely on ppc64le-unknown-linux-gnu par_bridge_recursion test sometimes hanging indefinitely Mar 5, 2024
@cuviper
Copy link
Member

cuviper commented Mar 5, 2024

I know it's hard in a koji builder, but the most useful thing would be a stack trace of all threads of the hung process.

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