adoptium / adoptium/infrastructure
test-aws-rhel76-armv8-1 fails tests with error: Couldn't find THPeligible in the smaps file
- Dominant language
- Python
- Stars
- 96
- Forks
- 106
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Please set the title to indicate the test name and machine name where known.
To make it easy for the infrastructure team to repeat and diagnose, please
answer the following questions:
- Test suite/name (e.g, BUILD_LIST, TARGET, CUSTOM_TARGET):
- gc/TestTransparentHugePagesHeap.java#Parallel
- gc/TestTransparentHugePagesHeap.java#G1
- gc/TestTransparentHugePagesHeap.java#Serial
- Recent `Test_` link to ci.adoptium.net that shows the failure: https://ci.adoptium.net/job/Test_openjdk25_hs_extended.openjdk_aarch64_linux_testList_0/70/
- Specific error text (if applicable):
```
02:49:49.204 stderr: [Exception in thread "main" java.lang.RuntimeException: Couldn't find THPeligible in the smaps file
02:49:49.204 at TestTransparentHugePagesHeap$VerifyTHPEnabledForHeap.main(TestTransparentHugePagesHeap.java:151)
```
- **Hyperlink** to re-run in Grinder: [Grinder rerun link](https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=-f+parallelList.mk+testList_0&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=Test_openjdk25_hs_extended.openjdk_aarch64_linux&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=5&VENDOR_TEST_DIRS=&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=aarch64_linux&GENERATE_JOBS=true&KEEP_REPORTDIR=true&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=test-aws-rhel76-armv8-1&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=v1.0.13-release&LIGHT_WEIGHT_CHECKOUT=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=25&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk25u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Frelease%2Fjobs%2Fjdk25u%2Fjdk25u-release-linux-aarch64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk-25.0.3%2B9_adopt&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=87&DOCKERIMAGE_TAG=&TEST_TIME=&JDK_IMPL=hotspot&SSH_AGENT_CREDENTIAL=&AUTO_DETECT=true&SLACK_CHANNEL=aqavit-bot&DYNAMIC_COMPILE=false&RELATED_NODES=&ADOPTOPENJDK_SYSTEMTEST_OWNER_BRANCH=adoptium%3Amaster&APPLICATION_OPTIONS=&CUSTOMIZED_SDK_URL_CREDENTIAL_ID=eclipse_temurin_bot_email_and_token&ARCHIVE_TEST_RESULTS=false&NUM_MACHINES=&OPENJDK_SHA=&TRSS_URL=&RERUN_FAILURE=false&USE_TESTENV_PROPERTIES=true&BUILD_LIST=openjdk&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=9&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None)
- Any existing issues covering this:
- Machine(s) this test works on: [test-docker-ubi8-armv8-2](https://ci.adoptium.net/computer/test-docker-ubi8-armv8-2) [test-docker-ubuntu2404-armv8-4](https://ci.adoptium.net/computer/test-docker-ubuntu2404-armv8-4)
- Machine(s) this test fails on: test-aws-rhel76-armv8-1
Any other details:
Bob suggests one cause could be an old kernel. Rhel 7.6 ships with kernel 3.10, and we need a Linux kernel that's at least 5.4
So the first step could be to run uname -r
Contributor guide
Research direction
Start with the linked CI failure and rerun information, then run `uname -r` on test-aws-rhel76-armv8-1 as suggested. Read the failing gc/TestTransparentHugePagesHeap.java tests and compare results with the working ARM machines. Done means identifying whether the machine's kernel explains the missing THPeligible entry and recording the diagnosis or next infrastructure action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, linux
- Domain
- infrastructure, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100