On Freitag, 23. Februar 2018, 09:19:51 CET wrote Olaf Hering:

Currently my SLE_12 repos in the xen prjs are in state "blocked", but the base prj is in state "published" since yesterday. I'm sure it will settle over the coming weekend. But I wonder why it takes so long for these other prjs to start build?

The base prj is done: # osc pr -q -r SLE_12 -a x86_64 home:olh:xen-buildrequires SLE_12 x86_64 (published)

All child prjs waiting for bison: # osc pr -q -r SLE_12 -a x86_64 home:olh:xen-unstable # osc pr -q -r SLE_12 -a x86_64 home:olh:xen-4.{2..10} SLE_12 x86_64 (blocked)

bison is long done: # osc buildhist -l 3 home:olh:xen-buildrequires bison SLE_12 x86_64 time srcmd5 vers-rel.bcnt rev duration 2017-12-01 11:59:48 ff5fd56c4d58210ca79c0a998c880b47 3.0.4-60.3 1 578 2018-02-21 08:02:47 ff5fd56c4d58210ca79c0a998c880b47 3.0.4-60.4 1 392 2018-02-21 08:41:20 ff5fd56c4d58210ca79c0a998c880b47 3.0.4-60.5 1 496

Not sure how to show at what time home:olh:xen-buildrequires reached state "published", which I think is the trigger for the other prjs to start building.

the publish state does not matter at all here.

but the repo event handling between projects have low prio in the scheduler, so it can take some time. I think it only helps improving the overall speed for the scheduler, we have still some ideas :)