8259924: GitHub actions fail on Linux x86_32 with "Could not configure libc6:i386"

[shipilev]

When libc6*:i386 packages are installed as the dependency of other packages, they seem to run into configure problems. It helps to install them ahead of the bulk of the packages to resolve this.

Current Linux x86 jobs fail like this:

E: Could not configure 'libc6:i386'.
E: Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8259924: GitHub actions fail on Linux x86_32 with "Could not configure libc6:i386"

Reviewers

• David Holmes (@dholmes-ora - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jdk pull/2128/head:pull/2128
$ git checkout pull/2128

[bridgekeeper]

👋 Welcome back shade! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@shipilev The following label will be automatically applied to this pull request:

• build

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 01: Full - Incremental (af23d95)
• 00: Full (e64adb4)

[dholmes-ora]

Seems reasonable - albeit annoying that we need to track some dependencies explicitly.

Thanks,
David

[openjdk]

@shipilev This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8259924: GitHub actions fail on Linux x86_32 with "Could not configure libc6:i386"

Reviewed-by: dholmes

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 1 new commit pushed to the master branch:

• 533a2d3: 8258961: move some fields of SafePointNode from public to protected

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[shipilev]

/integrate

[openjdk]

@shipilev Since your change was applied there have been 10 commits pushed to the master branch:

• 139f5d3: 8259035: Comments for load order of hsdis should be updated
• bd81ccf: 8259957: Build failure without C1 Compiler after JDK-8258004
• dfee7b8: 8259511: java/awt/Window/MainKeyWindowTest/TestMainKeyWindow.java failed with "RuntimeException: Test failed: 20 failure(s)"
• 14ce8f1: 8259870: zBarrier.inline.hpp should not include javaClasses.hpp
• a1a851b: Merge
• bb0821e: 8258643: [TESTBUG] javax/swing/JComponent/7154030/bug7154030.java failed with "Exception: Failed to hide opaque button"
• cd25bf2: 8259574: SIGSEGV in BFSClosure::closure_impl
• d5ca3b3: 8259641: C2: assert(early->dominates(LCA)) failed: early is high enough
• 492bebc: 8258004: Remove unnecessary inclusion of vm_version.hpp
• 533a2d3: 8258961: move some fields of SafePointNode from public to protected

Your commit was automatically rebased without conflicts.

Pushed as commit a9519c8.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.