Hilmar Preuße <[email protected]> writes: > On 3/2/26 19:59, Simon Josefsson wrote: > > Hello, > >> Hmm. Looking at timestamps in your log, it seems you only let the >> build+test phase run ~2-3 minutes?! Could you let it run for longer? >> The self-tests are not trivial, and often takes more time than that. I >> am not confident the 15m timeout is sufficient, but I didn't want to use >> an excessive long timeout in case 15m happened to be sufficient. >> > > I should be more clear, when reporting bugs. I did not test if the > auto-kill would have terminated the test suite after some time. I just > to report that the upgrade from TeXInfo 7.2 to 7.3 makes the auto-kill > necessary b/c the "/usr/bin/guile-3.0 .." command hangs (which is > probabyl not expected).
Ok. I don't think this has anything to do with TeXInfo 7.2->7.3, so please feel free to ignore this problem for that transition. I'm not sure a FTBFS when pressing ctrl-c during the build counts. It may be that the test will eventually succeed, within the 15 minutes timeout, if you let it run. I'll think about if we should just ignore the error code for all self-checks until we know more here, I see that even the latest upload fails in debci (which runs uncompiled code, so different from a 'make check' FTBFS during build, but still): https://ci.debian.net/packages/g/guile-fibers/unstable/amd64/68768475/ Running self-checks is known to be flaky, and I'm trying to report issues upstream but debugging this are hard because upstream is normally not using Debian and I suspect the real problem is some poor interaction between Guile, libc and/or kernel in Debian. And it rarely happens on my laptop. There are similar problems happens for several guile-related packages. /Simon
signature.asc
Description: PGP signature
