Status ticker fails to update periodically on some builds
Issue #107 (closed) appears to have been two independent issues.
The second part of this issue not targeted by buildstream/107-failing-child-processes-when-tracking-missing-git-branches is a UI freeze that occurs during certain builds.
Occasionally, during tracking, any timers in the status area may stop to count by themselves, only being updated by messages written to the main log. If run through bst build --track
, this will correct itself once an actual build starts.
I have not been able to track down the exact cause, but I believe this might be caused by a track job failing and the user choosing 'continue' or anything that causes https://gitlab.com/BuildStream/buildstream/blob/master/buildstream/_scheduler/job.py#L275.
I have been able to quite consistently reproduce this issue building gnome-modulesets (one of its sources currently fails to track due to an outdated SSL certificate), but I have been unable to reproduce it otherwise.