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:
echo "set man-db/auto-update false" | debconf-communicate
dpkg-reconfigure man-db
Platforms affected
Runner images affected
Image version and build link
Fri, 15 Nov 2024 17:03:46 GMT
Runner Image
Fri, 15 Nov 2024 17:03:46 GMT Image: ubuntu-24.04
Fri, 15 Nov 2024 17:03:46 GMT Version: 20241112.1.0
Fri, 15 Nov 2024 17:03:46 GMT Included Software: https://github.com/actions/runner-images/blob/ubuntu24/20241112.1/images/ubuntu/Ubuntu2404-Readme.md
Fri, 15 Nov 2024 17:03:46 GMT Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20241112.1
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.
name: Self-tests for scanners
on:
push:
branches:
- main
pull_request:
jobs:
man-db:
steps:
- run: |
sudo apt-get update
timeout 30s sudo apt-get --yes install python3-build
Description
This isn't necessarily a bug - more a performance enhancement request, but there's no category for that.
When running
apt installcommands 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 installActual behavior
man-db triggers do get run
Repro steps
Run the following workflow, note that it takes tends to timeout during the trigger processing.