Hi Paul, On 26/09/2022 19:46, Paul Gevers wrote:
The bug has a user specified for the usertag and explicitly mentions: """ Don't hesitate to reach out if you need help [...] """So, either using debian...@lists.debian.org or the submitter's address (mine) seems appropriate.
In which case, I evidently misunderstood. I had assumed that replying to the bug mail would do the same.
In this case:we can trigger the test from the backside, such that you can get a fresh log, but I prefer to only do that coordinated and after you give it a try to enable more diagnostic logging, because apparently in the original logs there wasn't enough information for you.I also offer to run the test (once or twice) manually and get information out of the testbed, if you tell me the exact commands you want me to run in the testbed.
Please trigger a new run. I can't add more diagnostics until I know where.What bothers me about this is that these flaky tests do not occur with the buildd hosts:
https://buildd.debian.org/status/logs.php?pkg=gscan2pdf&arch=all The only failure took 7 minutes, not 27 hours. So how do the CI hosts diff from the buildd ones? Thanks for your help. Regards Jeff
OpenPGP_signature
Description: OpenPGP digital signature
