autopkgtest failure due to timeout on rollup-plugin-node-polyfills
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| node-rollup-plugin-node-polyfills (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| ts-node (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
12 passing (8s)
1 failing
1) rollup-
works with zlib.js:
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/tmp/autopkgte
at Test.Runnable.
at done (/usr/share/
at /usr/share/
at next (evalmachine.
at evalmachine.
at Script.runInContext (vm.js:130:18)
at /tmp/autopkgtes
From the test history, 9.1.1-4 hit similar timeout-driven test failures and it appears a subsequent re-run of the test with the same trigger passed. Perhaps the timeout is too tight and could be loosened from 2000ms to, say 10000ms?
Looking at debian's test history, it appears to me to also have failures that resolve on a simple rerun, although can't be certain as there are not links to logs:
https:/
For now, I'm going to try a couple more re-triggers, but if it continues failing this way in the future, this may be worth adjusting timeouts and/or notifying Debian.
| Bryce Harrington (bryce) wrote | #1 |
| Brian Murray (brian-murray) wrote | #2 |
ts-node looks like it's the same situation.
https:/
46 passing (4m)
1 failing
1) ts-node
cli
should preserve `ts-node` context with child process:
Error: Timeout of 10000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/tmp/autopkgte
at Test.Runnable.
at Timeout.<anonymous> (/usr/share/
at listOnTimeout (internal/
at processTimers (internal/
Also of note that these two packages pass their tests on all other architectures, so this seems more likely to be a flaky test situation rather than an actual defect.