Le mar. 19 nov. 2024 à 09:33, Jérémy Lal <kapo...@melix.org> a écrit :
> Control: reassign -1 libuv1 > > Le lun. 18 nov. 2024 à 22:57, Jérémy Lal <kapo...@melix.org> a écrit : > >> Le lun. 18 nov. 2024 à 13:49, Santiago Vila <sanv...@debian.org> a >> écrit : >> >>> reassign 1087734 nodejs >>> found 1087734 20.18.0+dfsg-2 >>> retitle 1087734 nodejs: several nodejs packages hang the autobuilder >>> severity 1087734 grave >>> thanks >>> >>> Dear nodejs maintainers: >>> >>> Several nodejs packages have started to FTBFS randomly recently. >>> So far this is happening with these packages: >>> >>> jupyterlab >>> node-async >>> node-chart.js >>> node-dagre-d3-renderer >>> node-dagre-layout >>> node-miragejs >>> node-yjs >>> >>> This is reflected in the build logs by a line like this: >>> >>> E: Build killed with signal TERM after 60 minutes of inactivity >>> >>> which means sbuild decided to terminate the process because the >>> build did not end after a period of inactivity (in normal conditions, >>> those packages have typical build times of a few minutes, >>> so the 60 minutes timeout should be enough). >> >> > > This is a bug in libuv, which triggers a bug in the linux kernel, see: > https://github.com/libuv/libuv/issues/4598 > libuv has not yet decided if https://github.com/libuv/libuv/pull/4601 is the right fix. The linux kernel bug has been fixed in linux 6.1.116 and 6.6.60, see https://lore.kernel.org/io-uring/2024110620-stretch-custodian-0e7d@gregkh/ Jérémy
