Le dim. 7 déc. 2025 à 19:51, Paul Gevers <[email protected]> a écrit :
> Hi, > > On Sat, 6 Dec 2025 12:36:35 +0100 Santiago Vila <[email protected]> > 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 >
-- Pkg-javascript-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
