Skip to content

[integration_test] Address dpkg lock issues by setting DPkg::Lock::Timeout=600. #1986

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 5 commits into from
Jul 22, 2025
Merged

[integration_test] Address dpkg lock issues by setting DPkg::Lock::Timeout=600. #1986

merged 5 commits into from
Jul 22, 2025

Conversation

franciscovalentecastro
Copy link
Contributor

@franciscovalentecastro franciscovalentecastro commented Jul 21, 2025 •
edited
Loading

Description

Fix for Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? in Debian 11 integration tests.

Related issue

b/369656678

How has this been tested?

Checklist:

  • Unit tests
    • Unit tests do not apply.
    • Unit tests have been added/modified and passed for this PR.
  • Integration tests
    • Integration tests do not apply.
    • Integration tests have been added/modified and passed for this PR.
  • Documentation
    • This PR introduces no user visible changes.
    • This PR introduces user visible changes and the corresponding documentation change has been made.
  • Minor version bump
    • This PR introduces no new features.
    • This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
    • This PR bumps the version.

@franciscovalentecastro franciscovalentecastro changed the title [integration_tet] Trying to set DPkg::Lock::Timeout=100 again. [integration_tet] Trying to set DPkg::Lock::Timeout=600 again. Jul 21, 2025
@franciscovalentecastro franciscovalentecastro added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jul 21, 2025
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jul 21, 2025
@franciscovalentecastro franciscovalentecastro changed the title [integration_tet] Trying to set DPkg::Lock::Timeout=600 again. [integration_test] Trying to set DPkg::Lock::Timeout=600 again. Jul 21, 2025
@franciscovalentecastro franciscovalentecastro requested review from a team and jefferbrecht and removed request for a team July 22, 2025 14:08
@jefferbrecht
Copy link
Member

If this has a noticeable improvement then it's fine by me, but what about the approach we tried in #1827? I would expect that approach to work more generally; in this PR we'd have to instead add that override to every apt command. Do we understand why the old approach didn't work as well?

@franciscovalentecastro franciscovalentecastro changed the title [integration_test] Trying to set DPkg::Lock::Timeout=600 again. [integration_test] Address dpkg lock issues by setting DPkg::Lock::Timeout=600. Jul 22, 2025
@franciscovalentecastro
Copy link
Contributor Author

I don't know the specific reason of why the previous "global" approach of setting DPkg::Lock::Timeout was not working. I've found more documentation and examples on how to set it like -o DPkg::Lock::Timeout=600. Thank you for the review!