Source: node-reinterval
Version: 1.1.0-5
Severity: important
User: [email protected]
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed that it regularly fails, particularly on riscv64. The logs I check ran into a timeout. Is it possible to increase that?

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/n/node-reinterval/testing/riscv64/70002933/

241s autopkgtest [19:21:48]: test mocha-test: [-----------------------
246s
246s
246s   reInterval
247s     1) should work as an usual setInterval
247s     undefined should be able to clear an Interval (302ms)
248s     undefined should be able to reschedule an Interval (810ms)
248s
248s
248s   2 passing (2s)
248s   1 failing
248s
248s   1) reInterval
248s        should work as an usual setInterval:
248s      Error: Took too much (or not enough) time
248s       at Timeout._onTimeout (tests/test.js:18:18)
248s       at listOnTimeout (node:internal/timers:587:11)
248s       at process.processTimers (node:internal/timers:521:7)
248s
248s
248s
249s autopkgtest [19:21:56]: test mocha-test: -----------------------]

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to