Hi, Quoting Santiago Vila (2024-11-17 22:10:58) > See for example my build history for node-dagre-d3-renderer in trixie using > machines with 2 CPUs: > > Status: successful > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20240830T101510.571Z > Status: successful > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20240924T141820.007Z > Status: successful > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241006T140553.593Z > Status: successful > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241030T060505.673Z > Status: failed > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T010321.514Z > Status: failed > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T091551.769Z > Status: failed > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T091924.749Z > Status: failed > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T092942.053Z > Status: failed > node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T102025.563Z > > The failed build logs have this at the end: > > E: Build killed with signal TERM after 60 minutes of inactivity > > (probably related with the process which was not killed properly) > > Simple question: If I decide to use debbisect for this, how would the timeout > be handled? Does mmdebstrap have a timeout like sbuild?
mmdebstrap by itself does not have any built-in time-outs. And in debbisect only the (debvm-based) qemu runner has a built-in timeout, so you'd have to hack one yourself. You can use this script to bisect when a package started to FTBFS: /usr/share/doc/devscripts/examples/debbisect_buildsrc.sh Since you want to have a timeout, probably just copy the script somewhere and prefix the "apt-get source --build" with "timeout". Then run the whole thing as it says on the top of the file. I hope this helps. If debbisect doesn't work for you, bug reports to me please. :) Thanks! cheers, josch
signature.asc
Description: signature
