Buildbot failure in Wildebeest Builder on whole buildset

[Mark Wielaard]

Hi,

On Tue, Sep 07, 2021 at 11:34:16AM +0300, Dmitry V. Levin wrote:
> On Tue, Sep 07, 2021 at 02:12:18AM +0200, Mark Wielaard wrote:
> [...]
> > Subject: [PATCH] tests: Make sure to wait for initial scan and groom cycle
> > 
> > At startup the debuginfod server does a scan and groom cycle. Make
> > sure to wait for that before triggering a new one with SIGUSR1 or
> > SIGURST2.
> 
> Did you mean SIGUSR2?

Sigh. Yes, that was a typo. Sorry.

It seems this did help with the debuginfod testcases. But we were
still seeing some failures on some of the buildbots because it wasn't
early enough. We really should wait for the initial scan (and possibly
groom) cycle to be done before we make any changes to the scan
directories. Otherwise only part of them might be scanned (or groomed)
at the start (especially because some tests populate the scan dirs and
then remove some files, which aren't supported, again).

The attached (pushed) fixes that hopefully.

Cheers,

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-tests-Make-sure-to-wait-for-initial-scan-and-groom-c.patch
Type: text/x-diff
Size: 8772 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/elfutils-devel/attachments/20210908/9369382f/attachment.bin>