-
Notifications
You must be signed in to change notification settings - Fork 11
Closed
Labels
flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Note: #322 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: fc7e03f7a3d3f805d0e9b132c1b34b814d3ac598
buildURL: Build Status, Sponge
status: failed
Test output
Command failed with exit code 18: npm run system-test
Error: Command failed with exit code 18: npm run system-test
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 runSystemTest (build/test/system-test/test.clientlibs.js:71:5)
-> /workspace/test/system-test/test.clientlibs.ts:81:3
at async Context. (build/test/system-test/test.clientlibs.js:110:13)
-> /workspace/test/system-test/test.clientlibs.ts:123:7Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.Important issue which blocks shipping the next release. Will be fixed prior to next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.