sanity.external test fails consistently while running rm -f

[adamfarley]

Summary

sanity.external is now failing consistently due to the error detailed below.

@smlambert - Could you please tag the person who owns these tests? Thank you. :)

Details

Last pass:
16:46:42 openjdk version "11.0.20.1" 2023-08-24
16:46:42 OpenJDK Runtime Environment Temurin-11.0.20.1+1 (build 11.0.20.1+1)
16:46:42 OpenJDK 64-Bit Server VM Temurin-11.0.20.1+1 (build 11.0.20.1+1, mixed mode)
https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/599/consoleFull

First failure:
18:26:49 openjdk version "11.0.21-beta" 2023-10-17
18:26:49 OpenJDK Runtime Environment Temurin-11.0.21+4-202308261707 (build 11.0.21-beta+4-202308261707)
18:26:49 OpenJDK 64-Bit Server VM Temurin-11.0.21+4-202308261707 (build 11.0.21-beta+4-202308261707, mixed mode)
https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/600/console

Example failure:
https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/601/console

18:41:51       [exec] Reading package lists...
18:41:51       [exec] �[91mE: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
18:41:51       [exec] E: Sub-process returned an error code
18:41:52       [exec] The command '/bin/sh -c apt-get update 	&& apt-get install -qq -y --no-install-recommends software-properties-common 	&& apt-get install -qq -y --no-install-recommends gnupg 	&& add-apt-repository ppa:ubuntu-toolchain-r/test 	&& apt-get update 	&& apt-get install -y --no-install-recommends git wget tar 	&& rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
18:41:52       [exec] �[0m
18:41:52  
18:41:52  BUILD FAILED

[adamfarley]

Issue continues to occur.

https://ci.adoptium.net/job/Test_openjdk21_hs_sanity.external_x86-64_linux_testList_0/2/console

[adamfarley]

Still occurs: https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux_testList_0/5/console

One theory: this be an old issue revealed by a config change, as the test used to pass with this message around the same location:

debconf: delaying package configuration, since apt-utils is not installed

So maybe apt-utils is now installed beforehand, or included in the base image, and the package config now runs without delay and fails.

[adamfarley]

Ok, if we exclude this test (functional-test) the other targets can run, at least.

[adamfarley]

auto exclude test functional-test

[github-actions]

The specified test cannot be excluded. Action run: https://github.com/adoptium/aqa-tests/actions/runs/10287426860

[adamfarley]

auto exclude test example_functional

[adamfarley]

Running test to verify that the exclude suppresses the problem from the wider job:

https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux_testList_0/6/console

Ok, Auto excludes are meant to create PRs, not change the repo instantly.

Sadly it doesn't seem like either happened.

In the meanwhile, the github action did create a suitably modified branch, so here's a re-test using that branch.

https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux_testList_0/8/

Update: Looks like the run above expired because the upstream artifacts were expired.

After the September release, I should re-run this as a grinder. Changes: Make sure I use the auto-gen branch like I did here , and use the nightly jdk build.