Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable man-db dpkg trigger #10977

Open
5 of 15 tasks
lengau opened this issue Nov 15, 2024 · 3 comments
Open
5 of 15 tasks

Disable man-db dpkg trigger #10977

lengau opened this issue Nov 15, 2024 · 3 comments

Comments

@lengau
Copy link

lengau commented Nov 15, 2024

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:

image

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

  • Azure DevOps
  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner images affected

  • Ubuntu 20.04
  • Ubuntu 22.04
  • Ubuntu 24.04
  • macOS 12
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022

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
@vidyasagarnimmagaddi
Copy link
Contributor

Hi @lengau , we're looking into this issue , we will update on it ASAP. thank you !

lengau added a commit to lengau/playground that referenced this issue Nov 15, 2024
lengau added a commit to lengau/playground that referenced this issue Nov 15, 2024
lengau added a commit to lengau/playground that referenced this issue Nov 15, 2024
lengau added a commit to lengau/playground that referenced this issue Nov 15, 2024
lengau added a commit to lengau/playground that referenced this issue Nov 15, 2024
lengau added a commit to lengau/playground that referenced this issue Nov 15, 2024
lengau added a commit to lengau/playground that referenced this issue Nov 15, 2024
lengau added a commit to lengau/playground that referenced this issue Nov 15, 2024
@lengau
Copy link
Author

lengau commented Nov 15, 2024

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?

@subir0071
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants