-
-
Notifications
You must be signed in to change notification settings - Fork 309
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
abort in hydra-eval-jobs: Collecting from unknown thread #1186
Comments
Same issue on NixOS/nixpkgs@90cd545, also aarch64. |
Related: - <NixOS/nix#4178> - <NixOS/nix#4178 (comment)> - <NixOS/hydra#1186> Signed-off-by: Gaoyang Zhang <[email protected]>
The problem hits me today, and I managed to workaround this issue by adding a This workaround comes from NixOS/nix#4178 (comment). |
Can confirm I've encountered this issue right after migrating my server from x86_64 to aarch64 (while keeping the same config). |
We encountered this issue as well. We were able to work around it by refactoring the Nix expressions. |
Describe the bug
Evaluating my jobset (configuration for some of my NixOS systems) causes hydra-eval-jobs to
always(edit: not always! it ended up evaluating successfully after crashing like 30 times) abort in GC_push_all_stacks with the message "Collecting from unknown thread". (pthread_stop_world.c:754 in libgc.so). Executing the build manually with nix build finishes without problems.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The process doesn't abort and finishes evaluating the jobset correctly.
Hydra Server:
Please fill out this data as well as you can, but don't worry if you can't -- just do your best.
Additional context
Here's the core dump log from systemd. The exact stack trace is always different but it always ends up in GC_malloc_kind_global to GC_push_all_stacks where it ends up aborting.
The text was updated successfully, but these errors were encountered: