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). > I just tried to build three of them using the sbuild unshare backend, and I can't reproduce. I've put a collection of build logs here: > > https://people.debian.org/~sanvila/build-logs/nodejs/ > > In some cases, the failure happens 100% of the time here, > so I can offer a VM to reproduce if required (please > contact me privately for details). > Doing so... > One remarkable detail: My build environment is made from > VMs with 1 and 2 CPUs. In this case, building with 1 CPU > almost always suceeeds, and building with 2 CPUs almost > always fails. Maybe this is a hint of why it's happening. > Not sure, I'm building on my old mac with 4 cpu and export DEB_BUILD_OPTIONS="parallel=3" and can't see anything.
