Skip to content
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

pack and install: "after each" hook: cleanup staging for "should be able to webpack the library" failed #1481

Closed
flaky-bot bot opened this issue Oct 27, 2022 · 4 comments · Fixed by #1494
Assignees
Labels
flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Oct 27, 2022

Note: #1415 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.


commit: 89daaac
buildURL: Build Status, Sponge
status: failed

Test output
ENOTEMPTY: directory not empty, rmdir '/tmp/tmp-130-if4OANDyeyE0/node_modules'
Error: ENOTEMPTY: directory not empty, rmdir '/tmp/tmp-130-if4OANDyeyE0/node_modules'
    at Object.rmdirSync (fs.js:850:3)
    at rmkidsSync (node_modules/rimraf/rimraf.js:349:27)
    at rmdirSync (node_modules/rimraf/rimraf.js:329:7)
    at rimrafSync (node_modules/rimraf/rimraf.js:301:9)
    at /workspace/node_modules/rimraf/rimraf.js:336:39
    at Array.forEach ()
    at rmkidsSync (node_modules/rimraf/rimraf.js:336:26)
    at rmdirSync (node_modules/rimraf/rimraf.js:329:7)
    at rimrafSync (node_modules/rimraf/rimraf.js:301:9)
    at Object._cleanupCallback [as removeCallback] (node_modules/tmp/lib/tmp.js:356:16)
    at Context. (build/system-test/test.kitchen.js:70:24)
        -> /workspace/system-test/test.kitchen.ts:74:18
    at processImmediate (internal/timers.js:461:21)
@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Oct 27, 2022
@bcoe
Copy link
Contributor

bcoe commented Oct 28, 2022

Feel free to assign back to me if you don't have time, just doing triage.

I believe this will be a really small tweak, where we maybe just need to provide the recursive flag?

@danielbankhead
Copy link
Member

Thanks! Will get to this shortly

@danielbankhead
Copy link
Member

Strange, we currently set recursive as true (effectively):

stagingDir = tmp.dirSync({keep, unsafeCleanup: true});

@danielbankhead
Copy link
Member

Related discussion: raszi/node-tmp#276

I'll refactor and remove this dependency altogether using native tools, e.g. fsPromises.mkdtemp

danielbankhead added a commit that referenced this issue Nov 23, 2022
danielbankhead added a commit that referenced this issue Nov 29, 2022
* test: Use Native FS Temp Directory Tools

Fixes: #1481

* build: fix linkinator config fo 169.254.169.254

* revert: linkinator debug
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants