What do these changes do?

The Benchmark job has been getting cancelled at its 15 minute limit, so CodSpeed stopped reporting on some PRs (for example https://github.com/aio-libs/aiohttp/actions/runs/32157680880/job/95779217306). The job logs show it stuck right after the CodSpeed runner prints Installing packages: /tmp/valgrind-codspeed.deb, libc6-dbg; that is a plain apt-get update plus apt-get install libc6-dbg inside the runner with no timeout, and it has taken anywhere from 37 seconds to over 14 minutes on the same runner image today. It runs even after the runner restores valgrind from its cache, because the runner also checks dpkg -s libc6-dbg and the cache only copies files.

This adds a step that installs libc6-dbg before the CodSpeed action with a timeout and a retry loop, so a stalled mirror fails fast and retries instead of hanging; once it is registered in dpkg the runner finds it present after its cache restore and skips apt entirely. It also raises the job timeout to 30 minutes, since a slow install plus the ~9 minute benchmark suite already blew past 15 in one run.

Are there changes in behavior for the user?

No, CI only.

Is it a substantial burden for the maintainers to support this?

No; one extra workflow step and a timeout bump.

Related issue number

None.

Checklist

• I think the code is well written
• Unit tests for the changes exist N/A
• Documentation reflects the changes N/A
• If you provide code modification, please add yourself to CONTRIBUTORS.txt N/A
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the CHANGES/ folder

  • name it <issue_or_pr_num>.<type>.rst (e.g. 588.bugfix.rst)

  • if you don't have an issue number, change it to the pull request
    number after creating the PR

    • .bugfix: A bug fix for something the maintainers deemed an
      improper undesired behavior that got corrected to match
      pre-agreed expectations.
    • .feature: A new behavior, public APIs. That sort of stuff.
    • .deprecation: A declaration of future API removals and breaking
      changes in behavior.
    • .breaking: When something public is removed in a breaking way.
      Could be deprecated in an earlier release.
    • .doc: Notable updates to the documentation structure or build
      process.
    • .packaging: Notes for downstreams about unobvious side effects
      and tooling. Changes in the test invocation considerations and
      runtime assumptions.
    • .contrib: Stuff that affects the contributor experience. e.g.
      Running tests, building the docs, setting up the development
      environment.
    • .misc: Changes that are hard to assign to any of the above
      categories.

  • Make sure to use full sentences with correct case and punctuation,
    for example:

    Fixed issue with non-ascii contents in doctest text files
    -- by :user:`contributor-gh-handle`.

    Use the past tense or the present tense a non-imperative mood,
    referring to what's changed compared to the last released version
    of this project.