vmTestbase/gc/gctests/SoftReference/soft001/soft001.java FAILED in Test_openjdk17_hs_extended.openjdk_x86-64_linux
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
For some reason fails on certain machines: https://ci.adoptium.net/job/Grinder/15895/ - test-docker-fedora42-x64-1, https://ci.adoptium.net/job/Grinder/15894/ - test-ibmcloud-centosstream10-x64-1
but passes on others: test-ibmcloud-rhel7-x64-1
I note from stdout that on test-ibmcloud-rhel7-x64-1 it runs "16 threads", whereas the failing nodes it runs "8 threads".
**Failing Test Info**
Test Name: https://ci.adoptium.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_linux_rerun/63/
Test Duration: 1 hour
Machine it fails on: https://ci.adoptium.net/job/Grinder/15895/ - test-docker-fedora42-x64-1, https://ci.adoptium.net/job/Grinder/15894/ - test-ibmcloud-centosstream10-x64-1
Machines it passes on (if intermittent): test-ibmcloud-rhel7-x64-1
**Jenkins Test Job Info**
Jenkins Test Job Name: Test_openjdk17_hs_extended.openjdk_x86-64_linux_rerun
Jenkins Test Job URL: https://ci.adoptium.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_linux_rerun/63/
TRSS link for the build (if available):
**Deep History Link from TRSS (if available)**
** Rerun in Grinder Link (if available) or Steps to Reproduce**
[Rerun in Grinder](https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=hotspot_custom&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&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=x86-64_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=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=v1.0.11-release&LIGHT_WEIGHT_CHECKOUT=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=17&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk17u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Frelease%2Fjobs%2Fjdk17u%2Fjdk17u-release-linux-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=azure&CUSTOM_TARGET=vmTestbase%2Fgc%2Fgctests%2FSoftReference%2Fsoft001%2Fsoft001.java&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk-17.0.18%2B8_adopt&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&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=43&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None)
**Java Version output (from console output)**
**Relevant Console Output (showing exceptions/errors/crashes)**
**Attach or link to relevant artifacts**
In the case of test failures, the Jenkins Test Job has test_output.tar.gz artifacts that contain extra logs and core files in the case of crashes. Please download and inspect these files. Copy relevant files to an accessible location that can be linked to, or attach relevant files to this issue directly.
Contributor guide
Research direction
Start with vmTestbase/gc/gctests/SoftReference/soft001/soft001.java and rerun the linked Grinder job on the passing and failing machines. Inspect the Test_openjdk17_hs_extended.openjdk_x86-64_linux_rerun/63 logs and test_output.tar.gz, comparing the reported thread counts and environment details. Done means the cause is identified and the test is made reliable or the environment-specific limitation is documented with evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100