nx@npm:20.3.0 [78682] couldn't be built successfully (exit code 129)

[Tobbe]

Current Behavior

Our yarn 4 install command randomly fails with error 129 in GitHub Action CI/CD workflow. After retrying it 1-2 times it usually works.

This only happens within our CI/CD - locally on our working machines (macOS) we never see this issue.

Expected Behavior

Yarn install should always work and not fail randomly with this error (and no further logs).

GitHub Repo

No response

Steps to Reproduce

1. Submit a new PR to @redwoodjs/redwood
2. Wait for the CI jobs to start
3. In close to 100% of all cases you'll see the error reported above

Nx Report

First tried with nx 19.8.4

Node           : 20.18.1
OS             : darwin-arm64
Native Target  : aarch64-macos
yarn           : 4.4.0

nx          : 19.8.4
lerna       : 8.1.9
@nrwl/tao   : 19.8.4
typescript  : 5.6.2

Then upgraded to 19.8.14, but still run into the same issue

Node           : 20.18.1
OS             : darwin-arm64
Native Target  : aarch64-macos
yarn           : 4.4.0

nx          : 19.8.14
lerna       : 8.1.9
@nrwl/tao   : 19.8.14
typescript  : 5.6.2

Failure Logs

Run yarn install --inline-builds && yarn --cwd packages/create-redwood-rsc-app install --inline-builds
➤ YN0000: · Yarn 4.4.0
➤ YN0000: ┌ Resolution step
Resolution step
➤ YN0000: └ Completed in 0s 513ms
➤ YN0000: ┌ Post-resolution validation
Post-resolution validation
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
Fetch step
➤ YN0000: └ Completed in 11s 821ms
➤ YN0000: ┌ Link step
Link step
➤ YN0009: nx@npm:20.3.0 [78682] couldn't be built successfully (exit code 129, logs can be found here: /tmp/xfs-557bb8a4/build.log)
/tmp/xfs-557bb8a4/build.log
➤ YN0000: └ Completed in 47s 316ms
➤ YN0000: · Failed with errors in 1m 1s
Error: Process completed with exit code 1.

Full logs here: https://github.com/redwoodjs/redwood/actions/runs/12527448563/job/34941058589?pr=11845

Package Manager Version

yarn 4.4.0

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

This is the same as #27397 and I would have just continued the thread there, but that issue was locked, so I had to open a new one. Sorry for the noise.