<!-- Thank you for reporting a flaky test. Flaky tests are tests that fail occasionally in the Node.js CI, but not consistently enough to block PRs from landing, or that are failing in CI jobs or test modes that are not run for every PR. Please fill in as much of the template below as you're able. Test: The test that is flaky - e.g. `test-fs-stat-bigint` Platform: The platform the test is flaky on - e.g. `macos` or `linux` Console Output: A pasted console output from a failed CI job showing the whole failure of the test Build Links: Links to builds affected by the flaky test If any investigation has been done, please include any information found, such as how consistently the test fails, whether the failure could be reproduced locally, when the test started failing, or anything else you think is relevant. --> * **Test**: test.parallel/test-repl-history-navigation * **Platform**: [`node-test-commit-arm-fanned`](https://ci.nodejs.org/job/node-test-commit-arm-fanned/) * **Console Output:** ``` 19:29:04 not ok 499 parallel/test-repl-history-navigation 19:29:04 --- 19:29:04 duration_ms: 17.21 19:29:04 severity: fail 19:29:04 exitcode: 1 19:29:04 stack: |- 19:29:04 node:internal/timers:558 19:29:04 timer._onTimeout(...args); 19:29:04 ^ 19:29:04 19:29:04 TypeError: Found non-callable @@iterator 19:29:04 at listOnTimeout (node:internal/timers:558:17) 19:29:04 at processTimers (node:internal/timers:499:7) 19:29:04 ... ``` * **Build Links**: https://ci.nodejs.org/job/node-test-binary-arm-12+/9124/RUN_SUBSET=1,label=pi2-docker/testReport/junit/(root)/test/parallel_test_repl_history_navigation/
Activity
RaisinTen commentedon Feb 4, 2021
cc @nodejs/timers
timers: fix unsafe array iteration
timers: fix unsafe array iteration
timers: fix unsafe array iteration
timers: fix unsafe array iteration
timers: fix unsafe array iteration
timers: fix unsafe array iteration