jcstress_StampedLockPairwiseTests_0 FAILED in Test_openjdk21_hs_dev.system_x86-64_linux (timeout)
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
Console output (running on test-docker-ubuntu2204-x64-1):
```
[2024-02-16T10:51:43.613Z] (ETA: in 09:30:32; at Fri, 2024-02-16 20:22:15)
[2024-02-16T10:51:43.613Z] (Sampling Rate: 3.82 M/sec)
[2024-02-16T10:51:43.613Z] (JVMs: 0 starting, 2 running, 0 finishing)
[2024-02-16T10:51:43.613Z] (CPUs: 4 configured, 4 allocated)
[2024-02-16T10:51:43.613Z] (Results: 15300 planned; 3201 passed, 0 failed, 0 soft errs, 0 hard errs)
[2024-02-16T10:51:43.613Z]
[2024-02-16T10:51:58.410Z] Cancelling nested steps due to timeout
[2024-02-16T10:51:58.440Z] Sending interrupt signal to process
[2024-02-16T10:51:59.839Z] -----------------------------------
[2024-02-16T10:51:59.839Z] jcstress_StampedLockPairwiseTests_0_FAILED
[2024-02-16T10:51:59.839Z] -----------------------------------
```
**Test Info**
Test Name: jcstress_StampedLockPairwiseTests_0
Test Duration: 2 hr 31 min 18 sec
Machine: test-docker-ubuntu2204-x64-1
TRSS link for the test output: https://trss.adoptium.net/output/test?id=65cf44cb43ff67006eed2a06
**Build Info**
Build Name: Test_openjdk21_hs_dev.system_x86-64_linux
Jenkins Build start time: Feb 15 2024, 07:51 pm
Jenkins Build URL: https://ci.adoptium.net/job/Test_openjdk21_hs_dev.system_x86-64_linux/1/
TRSS link for the build: https://trss.adoptium.net/allTestsInfo?buildId=65cf41ab43ff67006eed001c
**Java Version**
openjdk version "21.0.3-beta" 2024-04-16
OpenJDK Runtime Environment Temurin-21.0.3+3-202402160037 (build 21.0.3-beta+3-ea)
OpenJDK 64-Bit Server VM Temurin-21.0.3+3-202402160037 (build 21.0.3-beta+3-ea, mixed mode, sharing)
[Rerun in Grinder](https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=jcstress_StampedLockPairwiseTests_0&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=false&KEEP_REPORTDIR=false&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=master&LIGHT_WEIGHT_CHECKOUT=true&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=21&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk21u%2Fjdk21u-linux-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk-21.0.3%2B3_adopt&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=&JDK_IMPL=hotspot&TEST_TIME=&SSH_AGENT_CREDENTIAL=&AUTO_DETECT=true&SLACK_CHANNEL=&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=&USE_TESTENV_PROPERTIES=false&BUILD_LIST=system&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=107&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=10&JVM_OPTIONS=&PARALLEL=None)
Contributor guide
Research direction
Start with the TRSS test output for jcstress_StampedLockPairwiseTests_0 and compare its timeout details with the linked Jenkins build. Rerun the test using the provided Grinder configuration to determine whether the timeout is reproducible. Done means identifying the cause and documenting or implementing a focused resolution for the failed test.
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
- 25/100