On Fri, 2026-08-07 at 19:17 +0000, Chris Laplante via lists.openembedded.org wrote: > I have noticed that some builds cause an avalanche of “Checking > sstate mirror object availability” messages to fill the screen, one > after another, preventing me from seeing the more useful per-task > progress bars. It also hides the “Currently n running tasks” progress > bar. > > This tends to happen a lot with builds that heavily utilize multiconfigs. > > My screen ends up looking like this: > > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:47 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:07 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:07 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:05 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:08 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:16 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:08 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:06 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:13 > Checking sstate mirror object availability: 100% > |#####################################################################################| > Time: 0:00:05 > … > > Does anyone actually find this particular progress bar useful? I > wonder if we can be more selective about when we show it. > Alternatively, maybe we can just tack it onto the end of the per-task > progress bar list?
These things are tough. Some people want progress bars for everything. Personally, I hate the complexity they add to the code, and that they're near impossible to make actually accurate. Access to sstate mirrors or hash equivalence can be slow and users do need some indication of what the system is doing rather than just sitting. Some sstate mirrors are fast, as it probably is in your case. We do already only show that bar when there are more than 100 recipes being queried iirc. I was asked to remove that piece and refused, for exactly this kind of reason. Next, you'll ask to make it configurable and go and cry quietly as it means more variables, more docs, more things to test and maintain and have break. I/we can't win :/ All that said, I'm open to trying to find a way to improve the output if we can work out the specific circumstances where it is poor and there is something that isn't too complex we can do about it. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#243028): https://lists.openembedded.org/g/openembedded-core/message/243028 Mute This Topic: https://lists.openembedded.org/mt/120648064/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
