turborepo: Turborepo hanging in CI
Verify canary release
- I verified that the issue exists in the latest Turborepo canary release.
Link to code that reproduces this issue
https://github.com/jakubmazanec/apps/pull/21
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Windows
Which canary version will you have in your reproduction?
2.0.0-canary.2
Describe the Bug
After updating from 1.10.3 to 1.13.3, Turborepo freezes on a test task during GitHub workflow run (which uses Linux; https://github.com/jakubmazanec/apps/actions/runs/9357742231/job/25758162977). I was unable to figure out why, nor any further details, since it is working locally on my Windows laptop. Also, I couldn’t actually check the canary version, since it has breaking changes and I cannot modify my config.
Expected Behavior
It works, like it is working on a version 1.10.3.
To Reproduce
In other issues I see mentions that Turborepo currently randomly freezes on Linux, so maybe it’s related?
Additional context
No response
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 13
- Comments: 60 (18 by maintainers)
Commits related to this issue
- Add CI to default passthroughs. (#8393) ### Description By convention, CI systems will set a `CI` environment variable. Given the ubiquity of this variable, there are some tools that rely on this... — committed to vercel/turborepo by anthonyshew 2 years ago
- chore: add trace level logging to process management (#8822) ### Description Add additional detailed logging to child process management to aid in finding issues causing https://github.com/vercel... — committed to vercel/turborepo by chris-olszewski 2 years ago
- fix: close stdin for non-interactive tasks (#8838) ### Description Fixes #8281 With this PR we now close `stdin` for any task that is not marked as `"interactive": true` or `"persistent": tru... — committed to yonasBSD/turbo by chris-olszewski 2 years ago
- chore: downgrade turbo to 1 2 is hanging https://github.com/vercel/turbo/issues/8281 — committed to repobuddy/repobuddy by unional 2 years ago
- chore: downgrade turbo to 1 2 is hanging https://github.com/vercel/turbo/issues/8281 — committed to repobuddy/repobuddy by unional 2 years ago
- chore: update turbo repro of https://github.com/vercel/turborepo/issues/8281 — committed to repobuddy/repobuddy by unional 2 years ago
Having the same issue in 2.1.3, tested with
--env-mode=loosebut no luckThese are the last lines of logs before it hangs
2.0.4-canary.0 seemed to have fix this error for me as well! Thank you 😃
(Was using turbo 2.0.3 before)
@R-Bower For us with 2.0.11 and
--env-mode=looseit still does not work at the moment.The log out put before it hangs is the following:
If those encountering this issue could try running with
-vvvon2.0.10-canary.0and provide the resulting logs that would be very helpful. I added many trace level logs around the area where the programs appear to be hanging.Setting TURBO_UI=false infront of
turbo runin my package.json script did not resolve the issue on turbo 2.0.5 - it’s still freezing.EDIT: turbo 2.0.7-canary.0 same thing
@Vincent-liuwingsang I think i resolved this by giving it a directory in the github action yaml and not running it with turbo
I was doing some repository cleanup. Those labels are from when Turbopack was also in this repository, so aren’t meaningful anymore. We still need figure out how to resolve this.
FYI, I see that you are using
process.report.getReport()to determine glibc, this has been known to cause freezes https://github.com/vercel/turborepo/blob/ba769dc14dbb556f6aace5c6c7c775ae894a2b1b/packages/turbo-repository/js/index.js#L29https://github.com/nodejs/node/issues/55576#issuecomment-2443914070
This has caused freeze issues in boh yarn and npm already, I suggest you check out https://github.com/npm/npm-install-checks/pull/120 which is a viable fix for npm, basically the getReport has to run before anything else in the program (like fetch for telemetry) and not be used after that
Though I’m not sure this is directly the cause of this particular freeze issue
-vvwould be great as well. If you’d like you could send me the logs atchris.olszewski@vercel.com.I have a case that it hangs too. Tried both
2.0.9and2.0.10-canary.1. It works in1.13.0https://github.com/repobuddy/repobuddy/tree/turbo-2-hang
it hangs when running the
testorcoveragescript in the./testcases/electron-tsor./testcases/electron-renderer-tsprojects.When running them directly, they produce these messages but the script passes and terminates properly:
This happens on both CI (ubuntu) and WSL (ubuntu)
It seems to be working for me now (version
2.0.10-canary.1). Great job @chris-olszewski, thank you for fixing this.@jakubmazanec noticing the same thing… we are trying to upgrade to
2.0.6from1.13.3and it hangs on both versions… rolled back to1.12.5and it worksthat fixed it for me! thank you 😃