Bug#1108810: [Pkg-javascript-devel] Bug#1108810: Bug#1108810: nodejs: FTBFS randomly: autobuilder hangs
Le dim. 7 déc. 2025 à 21:15, Paul Gevers a écrit : > Hi, > > On 12/7/25 21:07, Jérémy Lal wrote: > > The tests runner logs tests marked as "flaky" like the one you mention: > > all the tests with > > "not ok" TODO: Fix flaky test > > won't be accounted for. > > > Hmm, ok. So it only failed on the following? > 443s not ok 1372 parallel/test-http-keep-alive-empty-line > Yes That test should be marked as flaky, the parameters don't take into account the possibility of the environment being slow.
Bug#1108810: [Pkg-javascript-devel] Bug#1108810: Bug#1108810: nodejs: FTBFS randomly: autobuilder hangs
Hi, On 12/7/25 21:07, Jérémy Lal wrote: The tests runner logs tests marked as "flaky" like the one you mention: all the tests with "not ok" TODO: Fix flaky test won't be accounted for. Hmm, ok. So it only failed on the following? 443s not ok 1372 parallel/test-http-keep-alive-empty-line Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1108810: [Pkg-javascript-devel] Bug#1108810: Bug#1108810: nodejs: FTBFS randomly: autobuilder hangs
Le dim. 7 déc. 2025 à 19:51, Paul Gevers a écrit : > Hi, > > On Sat, 6 Dec 2025 12:36:35 +0100 Santiago Vila > wrote: > > On Fri, Dec 05, 2025 at 10:35:19PM +0100, Jérémy Lal wrote: > > > Source: nodejs > > > Followup-For: Bug #1108810 > > > Control: tags -1 ftbfs > > > > > > Is this still happening with forky/sid ? > > > > No, the random failures are not happening with version > > 22.21.1+dfsg+~cs22.19.0-5 (tried a lot of times in my setup this night > > to be sure). > > > > But they still happen in stable. What can we do about it? > > Related, I just saw a failing autopkgtest [1] (because it was marked as > a regression for glibc) that has this: > 1232s not ok 3789 > sequential/test-http-server-keep-alive-timeout-slow-client-headers # > TODO : Fix flaky test > > Maybe it would be best to mark all flaky tests as flaky, such that they > don't cause the whole autopkgtest to fail. If that's not possible in the > framework in use, maybe better don't run those tests in the autopkgtest. > The tests runner logs tests marked as "flaky" like the one you mention: all the tests with "not ok" TODO: Fix flaky test won't be accounted for. > Paul > > [1] https://ci.debian.net/packages/n/nodejs/testing/ppc64el/66892056/ > -- > Pkg-javascript-devel mailing list > [email protected] > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel >
Bug#1108810: [Pkg-javascript-devel] Bug#1108810: nodejs: FTBFS randomly: autobuilder hangs
Hi, On Sat, 6 Dec 2025 12:36:35 +0100 Santiago Vila wrote: On Fri, Dec 05, 2025 at 10:35:19PM +0100, Jérémy Lal wrote: > Source: nodejs > Followup-For: Bug #1108810 > Control: tags -1 ftbfs > > Is this still happening with forky/sid ? No, the random failures are not happening with version 22.21.1+dfsg+~cs22.19.0-5 (tried a lot of times in my setup this night to be sure). But they still happen in stable. What can we do about it? Related, I just saw a failing autopkgtest [1] (because it was marked as a regression for glibc) that has this: 1232s not ok 3789 sequential/test-http-server-keep-alive-timeout-slow-client-headers # TODO : Fix flaky test Maybe it would be best to mark all flaky tests as flaky, such that they don't cause the whole autopkgtest to fail. If that's not possible in the framework in use, maybe better don't run those tests in the autopkgtest. Paul [1] https://ci.debian.net/packages/n/nodejs/testing/ppc64el/66892056/ OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1108810: [Pkg-javascript-devel] Bug#1108810: nodejs: FTBFS randomly: autobuilder hangs
On Fri, Dec 05, 2025 at 10:35:19PM +0100, Jérémy Lal wrote: > Source: nodejs > Followup-For: Bug #1108810 > Control: tags -1 ftbfs > > Is this still happening with forky/sid ? No, the random failures are not happening with version 22.21.1+dfsg+~cs22.19.0-5 (tried a lot of times in my setup this night to be sure). But they still happen in stable. What can we do about it? Thanks.
Bug#1108810: nodejs: FTBFS randomly: autobuilder hangs
Source: nodejs Followup-For: Bug #1108810 Control: tags -1 ftbfs Is this still happening with forky/sid ?
Bug#1108810: [Pkg-javascript-devel] Bug#1108810: nodejs: FTBFS randomly: autobuilder hangs
Le sam. 5 juil. 2025 à 13:01, Santiago Vila a écrit : > Package: src:nodejs > Version: 20.19.2+dfsg-1 > Severity: important > Tags: ftbfs trixie sid > > Dear maintainer: > > During a rebuild of all packages in unstable, your package failed to build: > > > > [...] > debian/rules clean > dh clean >dh_auto_clean > make -j2 distclean > make[1]: Entering directory '/<>' > rm -f -r out > rm -f config.gypi icu_config.gypi > rm -f config.mk > rm -f -r node node_g > rm -f -r node_modules > rm -f -r deps/icu > rm -f -r deps/icu4c*.tgz deps/icu4c*.zip deps/icu-tmp > rm -f node-v20.19.2-linux-x64.tar.* node-v20.19.2.tar.* > make[1]: Leaving directory '/<>' > > [... snipped ...] > Oddly, I can't reproduce (tried six times today). In any case, there is a mistake in debian/rules, --timeout=6000 should be --timeout=1000 to make sure tests have enough time on riscv64 but don't go above 60 minutes which triggers a failure.
Bug#1108810: nodejs: FTBFS randomly: autobuilder hangs
Package: src:nodejs Version: 20.19.2+dfsg-1 Severity: important Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: [...] debian/rules clean dh clean dh_auto_clean make -j2 distclean make[1]: Entering directory '/<>' rm -f -r out rm -f config.gypi icu_config.gypi rm -f config.mk rm -f -r node node_g rm -f -r node_modules rm -f -r deps/icu rm -f -r deps/icu4c*.tgz deps/icu4c*.zip deps/icu-tmp rm -f node-v20.19.2-linux-x64.tar.* node-v20.19.2.tar.* make[1]: Leaving directory '/<>' [... snipped ...] duration_ms: 134.88000 ... ok 3462 sequential/test-child-process-emfile --- duration_ms: 261.53000 ... ok 3463 sequential/test-child-process-execsync --- duration_ms: 1007.65400 ... ok 3464 sequential/test-child-process-exit --- duration_ms: 807.32500 ... ok 3465 sequential/test-child-process-pass-fd --- duration_ms: 5071.90400 ... ok 3466 sequential/test-cli-syntax-bad --- duration_ms: 610.40800 ... ok 3467 sequential/test-cli-syntax-file-not-found --- duration_ms: 411.66700 ... ok 3468 sequential/test-cli-syntax-good --- duration_ms: 717.43300 ... ok 3469 sequential/test-cli-syntax-require --- duration_ms: 610.42100 ... ok 3470 sequential/test-cluster-inspect-brk --- duration_ms: 209.63100 ... ok 3471 sequential/test-cluster-net-listen-ipv6only-none --- duration_ms: 412.92300 ... ok 3472 sequential/test-cluster-net-listen-ipv6only-rr --- duration_ms: 408.84100 ... ok 3473 sequential/test-cluster-send-handle-large-payload --- duration_ms: 326.08100 ... ok 3474 sequential/test-cpu-prof-default --- duration_ms: 1308.33900 ... ok 3475 sequential/test-cpu-prof-dir-and-name --- duration_ms: 1307.36300 ... ok 3476 sequential/test-cpu-prof-dir-relative --- duration_ms: 1309.98700 ... ok 3477 sequential/test-cpu-prof-dir-worker # TODO : Fix flaky test --- duration_ms: 1507.77000 ... ok 3478 sequential/test-cpu-prof-drained --- duration_ms: 1307.76800 ... ok 3479 sequential/test-cpu-prof-exit --- duration_ms: 406.98900 ... ok 3480 sequential/test-cpu-prof-invalid-options --- duration_ms: 261.33200 ... ok 3481 sequential/test-cpu-prof-kill --- duration_ms: 406.97100 ... ok 3482 sequential/test-cpu-prof-name --- duration_ms: 1307.27800 ... ok 3483 sequential/test-cpu-prof-worker-argv --- duration_ms: 1407.64600 ... ok 3484 sequential/test-crypto-timing-safe-equal --- duration_ms: 134.94100 ... ok 3485 sequential/test-debug-prompt --- duration_ms: 609.57200 ... ok 3486 sequential/test-debugger-custom-port --- duration_ms: 707.24200 ... ok 3487 sequential/test-debugger-debug-brk --- duration_ms: 209.56400 ... ok 3488 sequential/test-debugger-invalid-args --- duration_ms: 5415.17500 ... ok 3489 sequential/test-debugger-launch --- duration_ms: 707.14700 ... ok 3490 sequential/test-debugger-pid --- duration_ms: 507.02900 ... ok 3491 sequential/test-deprecation-flags --- duration_ms: 514.89100 ... ok 3492 sequential/test-dgram-bind-shared-ports --- duration_ms: 409.66400 ... ok 3493 sequential/test-dgram-implicit-bind-failure --- duration_ms: 134.92500 ... ok 3494 sequential/test-dgram-pingpong --- duration_ms: 167.96300 ... ok 3495 sequential/test-diagnostic-dir-cpu-prof --- duration_ms: 2408.13700 ... ok 3496 sequential/test-diagnostic-dir-heap-prof --- duration_ms: 1808.32800 ... ok 3497 sequential/test-fs-opendir-recursive --- duration_ms: 209.86200 ... ok 3498 sequential/test-fs-readdir-recursive --- duration_ms: 209.55700 ... ok 3499 sequential/test-fs-stat-sync-overflow --- duration_ms: 326.01600 ... ok 3500 sequential/test-fs-watch # TODO : Fix flaky test --- duration_ms: 134.91800 ... ok 3501 sequential/test-gc-http-client --- duration_ms: 209.89300 ... ok 3502 sequential/test-gc-http-client-onerror --- duration_ms: 209.59300 ... ok 3503 sequential/test-gc-http-client-timeout --- duration_ms: 609.66200 ... ok 3504 sequential/test-get-heapsnapshot-options --- duration_ms: 1723.16600 ... ok 3505 sequential/test-heapdump --- duration_ms: 908.88200 ... ok 3506 sequential/test-heapdump-flag --- duration_ms: 807.53600 ... ok 3507 sequential/test-heapdump-flag-custom-dir --- duration_ms: 808.58200 ... ok 3508 sequential/test-http-econnrefused --- duration_ms: 168.01400 ... ok 3509 sequential/test-http-keep-alive-large-write --- duration_ms: 168.05500 ... ok 3510 sequential/test-http-keepalive-maxsockets --- duration_ms: 507.15900 ... ok 3511 sequential/test-http-regr-gh-2928 --- duration_ms: 168.05500 ... ok 3512 sequential/test-http-server-keep-alive-timeout-slow-client-headers --- duration_ms: 3409.58200 ... ok 3513 sequential/test-http-server-keep-alive-timeout
