Open lengau opened 1 week ago
Hi @lengau , we're looking into this issue , we will update on it ASAP. thank you !
Huh, so I can't reproduce this in a fresh repository (see: https://github.com/lengau/playground/actions/runs/11861145621/job/33057884286) on any Ubuntu version - it might vary depending on how much disk access is occurring in the background or something too?
Preliminary investigation looks okay to waive the auto-update of man-db in the runner setup. Will update once we complete our analysis on the same.
Description
This isn't necessarily a bug - more a performance enhancement request, but there's no category for that.
When running
apt install
commands on Ubuntu hosted runners, the runners spend about 45 seconds just processing man-db triggers:However, in very few cases are these runners ever going to actually use these man-db changes, so this is close to a minute of wasted time for each run.
Adding the following commands to the setup of each runner image would disable this trigger:
Platforms affected
Runner images affected
Image version and build link
Relevant step: https://github.com/canonical/starflow/actions/runs/11860374887/job/33055486302?pr=23#step:2:88
Is it regression?
no
Expected behavior
man-db triggers don't get run on
apt-get install
Actual behavior
man-db triggers do get run
Repro steps
Run the following workflow, note that it takes tends to timeout during the trigger processing.