nodejs-pubsub icon indicating copy to clipboard operation
nodejs-pubsub copied to clipboard

📦 pack and install: should be able to use the d.ts failed

Open flaky-bot[bot] opened this issue 3 years ago • 2 comments

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


commit: 8ae0867340fa8bbcdfb93bbf966bade70d53cb57 buildURL: Build Status, Sponge status: failed

Test output
Command failed with exit code 1: npm install --unsafe-perm
Error: Command failed with exit code 1: npm install --unsafe-perm
    at makeError (node_modules/execa/lib/error.js:60:11)
    at handlePromise (node_modules/execa/index.js:118:26)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Context. (build/system-test/install.js:39:9)
        -> /workspace/system-test/install.ts:40:5

flaky-bot[bot] avatar Oct 11 '22 08:10 flaky-bot[bot]

commit: ac5e7ef8f8cf887a54eac27e8f88241036d9a8bf buildURL: Build Status, Sponge status: failed

Test output
Command failed with exit code 1: npm install --unsafe-perm
Error: Command failed with exit code 1: npm install --unsafe-perm
    at makeError (node_modules/execa/lib/error.js:60:11)
    at handlePromise (node_modules/execa/index.js:118:26)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Context. (build/system-test/install.js:39:9)
        -> /workspace/system-test/install.ts:40:5

flaky-bot[bot] avatar Oct 12 '22 17:10 flaky-bot[bot]

Looks like this issue is flaky. :worried:

I'm going to leave this open and stop commenting.

A human should fix and close this.


When run at the same commit (ac5e7ef8f8cf887a54eac27e8f88241036d9a8bf), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

flaky-bot[bot] avatar Oct 16 '22 08:10 flaky-bot[bot]

Using a fresh install and Node 12, I'm unable to repro this locally. I tried both npm 6 and 8, no luck.

feywind avatar Nov 09 '22 20:11 feywind