-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
SIGBUS sometimes when running bun install
and nx postscript
runs
#14207
Comments
bun install
and nx postscript
runsbun install
and nx postscript
runs
Are you able to share an nx workspace that the issue reproduces in? I haven't been able to trigger this in a new workspace. |
Unfortunately not. The code is under NDA, and I tried spending several hours creating a repro. Since it's flaky, I have no idea what triggers it. However, it always complains about the NX post install scripts. So must have something to do with whatever NX is trying to run after install. |
Is there a way to create a memory dump of some sorts that doesn't contain sensitive information? |
I'm facing this issue too within my org. We're building private npm packages with nx & bun. The error only shows up when running Here's a failing workflow: I hope it's something trivial. :) 🤞 |
I forgot to add that, like in @ffMathy's case, the issue is flaky. Rerunning the workflow may or may not result in a complete run without issues. |
Thanks a lot for the repro, I can start looking into this. I'm noticing the CI machine is x86_64 Linux -- @ffMathy is that the kind of machine that you got this on, too? You said it's a dev container; what was the host platform? |
For me, the host platform is a MacBook M1. But it happens on my GitHub Actions build too, which is an ubuntu-latest that is also running Bun commands inside a devcontainer via the official "devcontainers/ci" action. |
The base image of the devcontainer is node:lts. |
And is the container also running ARM, or is it emulated x86? |
The container is also running ARM. But in the CI environment where it's also happening in ubuntu-latest, both host and container is in X86. |
Thanks again for the repro @Leolainen, that was invaluable. After some debugging I think this is a duplicate of nrwl/nx#26517. In the meantime, a workaround that worked for me and for a few people in that issue thread is forcing the install scripts to run sequentially. You can do that in Bun by passing |
Pretty confident this is an upstream bug in nx that we are unable to help with much on our end If you think there's anything we can do to help, please leave a comment and we'll re-open this |
Sorry, I never responded. @190n Your suggestion seems to have solved the issue. Thanks a lot. :) |
What version of Bun is running?
1.1.29+6d43b3662
What platform is your computer?
Linux 6.10.4-linuxkit aarch64 unknown
What steps can reproduce the bug?
N/A - it happens inconsistently. We're running inside a DevContainer.
What is the expected behavior?
Bun install succeeds.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: