Pipeline results in pnpm: ENOTEMPTY: directory not empty error in GitHub Action runs
#9067
Replies: 2 comments 2 replies
-
|
I have a similar issue with a The most common error message looks like this run However, I did get a "directory not empty, rename" when I enabled debug logging. I was able to replicate the issue with Turborepo 2.0.0. Trying with v1.13.4 failed because the turbo.json format changed. I couldn't find docs describing Turbo v1.x - related - and so I stopped there (because I was never on v1.x and have nothing to roll back to). |
Beta Was this translation helpful? Give feedback.
-
|
Ulgh. Won't help OP, but my turbo.json used transit nodes: {
"$schema": "https://turbo.build/schema.json",
"tasks": {
"tsc-build": {
"dependsOn": ["transit"],
"outputs": ["lib/**"]
},
"transit": {
"dependsOn": ["^transit"]
}
}
}which is more or less what's recommended by the docs: {
"tasks": {
"topo": {
"dependsOn": ["^topo"]
},
"check-types": {
"dependsOn": ["topo"]
},
},
}I started deleting a ton of code in an attempt to minify the problem scope, and eventually discovered that the task was running out-of-topological-order: https://github.com/AlexErrant/Pentive/actions/runs/10744153624/job/29800451609
"tsc-build": {
"dependsOn": ["transit", "^tsc-build"],
"outputs": ["lib/**"]
},This, of course, is not recommended:
This is the branch where I minified the problem. Strangely, the initial run linked in my parent comment correctly runs |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the additional context here @AlexErrant ! I'm unclear whether something similar is happnening in my case as I don't really have topological order, each package can build independently, but this is helpful to chew on. |
Beta Was this translation helpful? Give feedback.
-
|
I finally found my root cause. I stared really, really, really hard at the lines before the error: Why am I fetching Node during a Turbo run? I already have Turns out I had set
So I deleted the config and everything worked as expected, including the transit nodes. Yay. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Ever since updating to Turbo v2, we've seen our tasks result in issues related to the following error message:
Our
turbo.jsonis as follows:{ "$schema": "https://turbo.build/schema.json", "globalDependencies": [".env", ".env.local"], "tasks": { "build": { "dependsOn": ["^build"], "outputs": [ "dist/**", "storybook-static/**", ".next/**", "!.next/cache/**" ] }, "test": {}, "lint": {}, "dev": { "cache": false, "persistent": true }, "clean": { "cache": false } } }Our root
package.jsonis as follows:{ "name": "<repo>", "devDependencies": { ... "turbo": "2.0.14" }, "engines": { "node": "20.12.2" }, "packageManager": "pnpm@9.9.0+sha512.60c18acd138bff695d339be6ad13f7e936eea6745660d4cc4a776d5247c540d0edee1a563695c183a66eb917ef88f2b4feb1fc25f32a7adcadc7aaf3438e99c1", "scripts": { "build": "turbo run build", "ci": "turbo run test lint", "clean": "turbo run clean && rm -rf node_modules", "deploy": "turbo run build", "dev": "turbo run dev --concurrency 11", "lint": "turbo run lint", "test": "turbo run test" } }When running
pnpm run ciin GitHub Actions, for example, we receive the error highlighted above. Instead, when we run it explicitly as seen below, everything seems to work without incident; however I don't believe this to be a long-term solution as it seems to defeat the purpose of a tool like turbo:Are we configuring turbo incorrectly? Is this a known issue with v2? Any help would be greatly appreciated 👍
Additional information
FWIW, here is an example of what a
lintscript looks like in a given workspaceSimilarly, the result of running
turbo run buildproduced the sameENOTEMPTYissue, it is not isolated to thetest,lint, orbuildjobs specifically, it appears to happen across the board.Example
No response
Beta Was this translation helpful? Give feedback.
All reactions