On Tue, Jun 07, 2022 at 03:17:12PM -0700, Vagrant Cascadian wrote: > On 2022-06-06, Chris Lamb wrote: > > Vagrant, do you have --profile output, out of interest? It would be > > interesting, for instance, if the HTML generation was taking so long > > that even if diffoscope stopped recursing into subarchives, it hit > > Jenkins' hard timeout. This may suggest that there is a bug in the > > HTML generation, and/or that the --timeout value on tests.r-b.org has > > not been set low enough relative to the hard timeout. > > Yeah, I think maybe we should add more time to the hard jenkins timeout > to make sure it really gets *some* output. > > The original was just the defaults that reprotest uses (perhaps we > should add --profile?).
Just mentioning that we already call diffoscope with --profile on
jenkins, just that if it gets killed hard it won't print it out.
Furthermore, there are 6 minutes (i.e. 0.1 hours) between SIGTERM and
SIGKILL. I don't know at which stage of this case diffoscope was
terminated, but perhaps it's one side that could be investiage: to make
diffoscope output something on SIGTERM when it still has a chance to
continue running.
> ## output (total time: 12.131s)
> 12.131s 1 call text
vs
> ## output (total time: 413.571s)
> 413.571s 1 call html
So it's not really the presenter that takes excessively. But otoh 413
seconds are more than 6 minutes. If somebody looks into the point above
I can change jenkins to wait 12 minutes (or 18) before KILLing after the
TERM signal.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
