sanity.external fails on ppc64le_linux with exit code 132
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
Example from https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_ppc64le_linux/9/console
```
12:38:36 [exec] ERROR: failed to solve: process "/bin/sh -c apt-get update \t&& apt-get install -qq -y --no-install-recommends software-properties-common \t&& apt-get install -qq -y --no-install-recommends gnupg \t&& add-apt-repository ppa:ubuntu-toolchain-r/test \t&& apt-get update \t&& apt-get install -y --no-install-recommends ant-optional maven git wget tar \t&& rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 132
12:38:36
```
Contributor guide
Research direction
Start with the linked Test_openjdk11_hs_sanity.external_ppc64le_linux/9 console output and inspect the failing external-test setup command containing apt-get and /bin/sh. Trace that setup in the aqa-tests test infrastructure, then verify that sanity.external completes successfully on ppc64le_linux without exit code 132.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100