ECM unittest fails, why?

Johan Ouwerkerk jm.ouwerkerk at gmail.com
Tue Mar 24 16:54:11 GMT 2020


On Tue, Mar 24, 2020 at 4:07 PM Friedrich W. H. Kossebau
<kossebau at kde.org> wrote:
>
> Am Dienstag, 24. März 2020, 08:37:56 CET schrieb Ben Cooksley:
> > On Tue, Mar 24, 2020 at 7:48 PM Friedrich W. H. Kossebau
> >
> > <kossebau at kde.org> wrote:
> > > Why CI does this order, but not locally for us, no clue so far.
> >
> > Could this ordering be a race condition by any chance?
> >
> > Two of the three nodes that perform the builds on the CI system are
> > 3rd generation Ryzen 7 systems (Octa Cores) with NVMe storage, so
> > there is a possibility this is the case...
>
> There is only one thread/job queue here when make is run if I saw correctly.
> So no race here I think. It might be rather something which determines the
> order of otherwise same-level targets handled, something like unsorted hash
> table layout, random number generation seed, something of that kind,
>

Perhaps the order in which directory entries are returned, which would
depend on inode creation?

Regards,

- Johan


More information about the Kde-buildsystem mailing list