Test_openjdk8_hs_sanity.system_arm_linux
Started by upstream project "build-scripts/jobs/jdk8u/jdk8u-linux-arm-temurin" build number 484
originally caused by:
Started by upstream project "build-scripts/openjdk8-pipeline" build number 3007
originally caused by:
Started by upstream project "build-scripts/utils/betaTrigger_8ea_arm32Linux" build number 241
originally caused by:
Started by timer
Checking out git ${ADOPTOPENJDK_REPO} into /home/jenkins/.jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux@script/7d272c0688f17ab4e5b2f6ce77a7dc9cf4df33ff05c3a95eddd38682ef795b79 to read aqa-tests/buildenv/jenkins/openjdk_tests
The recommended git tool is: git
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Using shallow clone with depth 1
Cloning repository https://github.com/adoptium/aqa-tests.git
> git init /home/jenkins/.jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux@script/7d272c0688f17ab4e5b2f6ce77a7dc9cf4df33ff05c3a95eddd38682ef795b79/aqa-tests # timeout=10
Fetching upstream changes from https://github.com/adoptium/aqa-tests.git
> git --version # timeout=10
> git --version # 'git version 2.43.0'
> git fetch --tags --force --progress --depth=1 -- https://github.com/adoptium/aqa-tests.git +refs/heads/*:refs/remotes/origin/* # timeout=60
> git config remote.origin.url https://github.com/adoptium/aqa-tests.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision c2cb30403aceac91d61b1840daf93f32093c42fc (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f c2cb30403aceac91d61b1840daf93f32093c42fc # timeout=10
Commit message: "Leverage getDependencies for dacapo.zip (#6337)"
> git rev-list --no-walk c1fd79c1ed8c98a6adc91439b16d862a27c6ac2f # timeout=10
First time build. Skipping changelog.
[Pipeline] Start of Pipeline
[Pipeline] timestamps
[Pipeline] {
[Pipeline] echo
[2025-06-19T20:49:28.070Z] SPEC: linux_arm
[Pipeline] echo
[2025-06-19T20:49:28.071Z] LABEL: ci.role.test&&sw.os.linux&&hw.arch.aarch32
[Pipeline] stage
[Pipeline] { (Queue)
[Pipeline] nodesByLabel
[2025-06-19T20:49:28.085Z] Found a total of 8 nodes with the 'ci.role.test&&sw.os.linux&&hw.arch.aarch32' label
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named dynamicAgents (to a value of type ArrayList) which could lead to memory leaks or other issues.
[Pipeline] echo
[2025-06-19T20:49:28.089Z] dynamicAgents: []
[Pipeline] node
[2025-06-19T20:49:31.618Z] Running on test-docker-ubuntu2404-armv7-7 in /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux
[Pipeline] {
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named ref_cache (to a value of type GStringImpl) which could lead to memory leaks or other issues.
[Pipeline] retry
[Pipeline] {
[Pipeline] timeout
[2025-06-19T20:49:31.632Z] Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] cleanWs
[2025-06-19T20:49:31.904Z] [WS-CLEANUP] Deleting project workspace...
[2025-06-19T20:49:31.905Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration...
[2025-06-19T20:49:32.032Z] [WS-CLEANUP] done
[Pipeline] }
[Pipeline] // timeout
[Pipeline] checkout
[2025-06-19T20:49:32.181Z] The recommended git tool is: git
[2025-06-19T20:49:32.444Z] No credentials specified
[2025-06-19T20:49:32.573Z] Cloning the remote Git repository
[2025-06-19T20:49:32.812Z] Cloning repository https://github.com/adoptium/aqa-tests.git
[2025-06-19T20:49:32.813Z] > git init /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests # timeout=10
[2025-06-19T20:49:32.824Z] [WARNING] Reference path does not exist: /home/jenkins/openjdk_cache
[2025-06-19T20:49:32.824Z] Fetching upstream changes from https://github.com/adoptium/aqa-tests.git
[2025-06-19T20:49:32.824Z] > git --version # timeout=10
[2025-06-19T20:49:32.836Z] > git --version # 'git version 2.43.0'
[2025-06-19T20:49:32.836Z] > git fetch --tags --force --progress -- https://github.com/adoptium/aqa-tests.git +refs/heads/*:refs/remotes/origin/* # timeout=10
[2025-06-19T20:49:39.803Z] Avoid second fetch
[2025-06-19T20:49:39.940Z] Checking out Revision c2cb30403aceac91d61b1840daf93f32093c42fc (origin/master)
[2025-06-19T20:49:39.578Z] > git config remote.origin.url https://github.com/adoptium/aqa-tests.git # timeout=10
[2025-06-19T20:49:39.586Z] > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2025-06-19T20:49:39.868Z] > git rev-parse origin/master^{commit} # timeout=10
[2025-06-19T20:49:40.004Z] > git config core.sparsecheckout # timeout=10
[2025-06-19T20:49:40.009Z] > git checkout -f c2cb30403aceac91d61b1840daf93f32093c42fc # timeout=10
[2025-06-19T20:49:41.438Z] Commit message: "Leverage getDependencies for dacapo.zip (#6337)"
[Pipeline] }
[Pipeline] // retry
[Pipeline] load
[Pipeline] { (/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/buildenv/jenkins/JenkinsfileBase)
[Pipeline] }
[Pipeline] // load
Did you forget the `def` keyword? WorkflowScript seems to be setting a field named jenkinsfile (to a value of type Script1) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named TIME_LIMIT (to a value of type Integer) which could lead to memory leaks or other issues.
[Pipeline] timeout
[2025-06-19T20:49:43.301Z] Timeout set to expire in 1 day 1 hr
[Pipeline] {
[Pipeline] echo
[2025-06-19T20:49:43.322Z] runMulticastCmd: false
[Pipeline] stage
[Pipeline] { (Setup)
[Pipeline] sh
[2025-06-19T20:49:44.891Z] + LC_TIME=C date +%a, %d %b %Y %T %z
[Pipeline] echo
[2025-06-19T20:49:45.409Z] PROCESSCATCH: Terminating any hung/left over test processes:
[Pipeline] sh
[2025-06-19T20:49:46.930Z] + aqa-tests/terminateTestProcesses.sh jenkins
[2025-06-19T20:49:46.930Z] Unix type machine..
[2025-06-19T20:49:46.930Z] Running on a Linux host
[2025-06-19T20:49:46.930Z] Woohoo - no rogue processes detected!
Did you forget the `def` keyword? Script1 seems to be setting a field named OPENJ9_REPO (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named TKG_REPO (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named TKG_BRANCH (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named OPENJ9_BRANCH (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named PLATFORM (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named CLONE_OPENJ9 (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named CUSTOM_TARGET (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named UPSTREAM_JOB_NAME (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named UPSTREAM_JOB_NUMBER (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named SSH_AGENT_CREDENTIAL (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named KEEP_WORKSPACE (to a value of type Boolean) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named OPENJ9_SHA (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named CLOUD_PROVIDER (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named SDK_RESOURCE (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named ITERATIONS (to a value of type Integer) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named NUM_MACHINES (to a value of type Integer) which could lead to memory leaks or other issues.
[Pipeline] sh
[2025-06-19T20:49:49.328Z] + printenv
[2025-06-19T20:49:49.328Z] JENKINS_HOME=/home/jenkins/.jenkins
[2025-06-19T20:49:49.328Z] OPENJ9_REPO=https://github.com/eclipse-openj9/openj9.git
[2025-06-19T20:49:49.328Z] SETUP_JCK_RUN=false
[2025-06-19T20:49:49.328Z] USE_TESTENV_PROPERTIES=false
[2025-06-19T20:49:49.328Z] EXTERNAL_CUSTOM_BRANCH=master
[2025-06-19T20:49:49.328Z] SSH_CLIENT=78.47.239.97 53690 22
[2025-06-19T20:49:49.328Z] USER=jenkins
[2025-06-19T20:49:49.328Z] BUILD_LIST=system
[2025-06-19T20:49:49.328Z] SDK_RESOURCE=upstream
[2025-06-19T20:49:49.328Z] OPENJ9_BRANCH=master
[2025-06-19T20:49:49.328Z] CI=true
[2025-06-19T20:49:49.328Z] RUN_CHANGES_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.system_arm_linux/463/display/redirect?page=changes
[2025-06-19T20:49:49.328Z] ADOPTOPENJDK_REPO=https://github.com/adoptium/aqa-tests.git
[2025-06-19T20:49:49.328Z] UPSTREAM_JOB_NUMBER=484
[2025-06-19T20:49:49.328Z] TARGET=sanity.system
[2025-06-19T20:49:49.328Z] EXIT_FAILURE=false
[2025-06-19T20:49:49.328Z] NODE_LABELS=armv8 hw.arch.aarch32 test test-docker-ubuntu2404-armv7-7 ci.role.test ubuntu linux armv8.2 hw.dockerhost.arm.dockerhost-equinix-ubuntu2204-armv8-1 sw.os.linux arm
[2025-06-19T20:49:49.328Z] HUDSON_URL=https://ci.adoptium.net/
[2025-06-19T20:49:49.328Z] USE_JRE=false
[2025-06-19T20:49:49.328Z] OLDPWD=/home/jenkins
[2025-06-19T20:49:49.328Z] STF_OWNER_BRANCH=adoptium:master
[2025-06-19T20:49:49.328Z] HOME=/home/jenkins
[2025-06-19T20:49:49.328Z] ADOPTOPENJDK_BRANCH=master
[2025-06-19T20:49:49.328Z] BUILD_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.system_arm_linux/463/
[2025-06-19T20:49:49.328Z] TAP_NAME=Test_openjdk8_hs_sanity.system_arm_linux.tap
[2025-06-19T20:49:49.328Z] JDK_IMPL=hotspot
[2025-06-19T20:49:49.328Z] DOCKER_REQUIRED=false
[2025-06-19T20:49:49.328Z] HUDSON_COOKIE=60713879-ae66-4070-af31-c557831ab720
[2025-06-19T20:49:49.328Z] JENKINS_SERVER_COOKIE=durable-d291f5ec4829c8229e2ccb033bc740b9efbbc122f65b46a7a4d4f4ced645e41a
[2025-06-19T20:49:49.328Z] PERF_ROOT=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../benchmarks
[2025-06-19T20:49:49.328Z] JDK_REPO=https://github.com/adoptium/aarch32-jdk8u
[2025-06-19T20:49:49.328Z] WORKSPACE=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux
[2025-06-19T20:49:49.328Z] KEEP_WORKSPACE=false
[2025-06-19T20:49:49.328Z] ARCHIVE_TEST_RESULTS=false
[2025-06-19T20:49:49.328Z] GENERATE_JOBS=true
[2025-06-19T20:49:49.328Z] TKG_OWNER_BRANCH=adoptium:master
[2025-06-19T20:49:49.328Z] PERSONAL_BUILD=false
[2025-06-19T20:49:49.328Z] LOGNAME=jenkins
[2025-06-19T20:49:49.328Z] NODE_NAME=test-docker-ubuntu2404-armv7-7
[2025-06-19T20:49:49.328Z] RUN_ARTIFACTS_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.system_arm_linux/463/display/redirect?page=artifacts
[2025-06-19T20:49:49.328Z] STAGE_NAME=Setup
[2025-06-19T20:49:49.328Z] AUTO_DETECT=true
[2025-06-19T20:49:49.328Z] EXECUTOR_NUMBER=0
[2025-06-19T20:49:49.328Z] JDK_VERSION=8
[2025-06-19T20:49:49.328Z] EXTERNAL_TEST_CMD=mvn clean install
[2025-06-19T20:49:49.328Z] RUN_TESTS_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.system_arm_linux/463/display/redirect?page=tests
[2025-06-19T20:49:49.328Z] BUILD_DISPLAY_NAME=#463
[2025-06-19T20:49:49.328Z] CUSTOMIZED_SDK_URL_CREDENTIAL_ID=eclipse_temurin_bot_email_and_token
[2025-06-19T20:49:49.328Z] TIME_LIMIT=25
[2025-06-19T20:49:49.328Z] HUDSON_HOME=/home/jenkins/.jenkins
[2025-06-19T20:49:49.328Z] JOB_BASE_NAME=Test_openjdk8_hs_sanity.system_arm_linux
[2025-06-19T20:49:49.328Z] PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
[2025-06-19T20:49:49.328Z] PLATFORM=arm_linux
[2025-06-19T20:49:49.328Z] TKG_ITERATIONS=1
[2025-06-19T20:49:49.328Z] EXIT_SUCCESS=false
[2025-06-19T20:49:49.328Z] BUILD_ID=463
[2025-06-19T20:49:49.328Z] RERUN_FAILURE=true
[2025-06-19T20:49:49.328Z] ACTIVE_NODE_TIMEOUT=5
[2025-06-19T20:49:49.328Z] BUILD_TAG=jenkins-Test_openjdk8_hs_sanity.system_arm_linux-463
[2025-06-19T20:49:49.328Z] SYSTEM_LIB_DIR=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:49:49.328Z] JENKINS_URL=https://ci.adoptium.net/
[2025-06-19T20:49:49.328Z] OPENJCEPLUS_GIT_REPO=https://github.com/ibmruntimes/OpenJCEPlus.git
[2025-06-19T20:49:49.328Z] LANG=C.UTF-8
[2025-06-19T20:49:49.328Z] JOB_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.system_arm_linux/
[2025-06-19T20:49:49.328Z] KEEP_REPORTDIR=false
[2025-06-19T20:49:49.328Z] JCK_GIT_BRANCH=master
[2025-06-19T20:49:49.328Z] ORIGIN_JDK_VERSION=8
[2025-06-19T20:49:49.328Z] BUILD_NUMBER=463
[2025-06-19T20:49:49.328Z] JENKINS_NODE_COOKIE=84ff3af9-aa3e-4776-8cae-1b2d17294d07
[2025-06-19T20:49:49.328Z] SHELL=/bin/sh
[2025-06-19T20:49:49.328Z] ITERATIONS=1
[2025-06-19T20:49:49.328Z] OPENJCEPLUS_GIT_BRANCH=semeru-java8
[2025-06-19T20:49:49.328Z] TEST_JDK_HOME=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image
[2025-06-19T20:49:49.328Z] RUN_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.system_arm_linux/463/display/redirect
[2025-06-19T20:49:49.328Z] OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse:master
[2025-06-19T20:49:49.328Z] SPEC=linux_arm
[2025-06-19T20:49:49.328Z] LIGHT_WEIGHT_CHECKOUT=false
[2025-06-19T20:49:49.328Z] HUDSON_SERVER_COOKIE=2d832652af5afba8
[2025-06-19T20:49:49.328Z] JOB_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_sanity.system_arm_linux/display/redirect
[2025-06-19T20:49:49.328Z] UPSTREAM_JOB_NAME=build-scripts/jobs/jdk8u/jdk8u-linux-arm-temurin
[2025-06-19T20:49:49.328Z] JOB_NAME=Test_openjdk8_hs_sanity.system_arm_linux
[2025-06-19T20:49:49.328Z] SLACK_CHANNEL=aqavit-bot
[2025-06-19T20:49:49.328Z] ADOPTOPENJDK_SYSTEMTEST_OWNER_BRANCH=adoptium:master
[2025-06-19T20:49:49.328Z] PWD=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux
[2025-06-19T20:49:49.328Z] LIB_DIR=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/lib
[2025-06-19T20:49:49.328Z] TEST_TIME=120
[2025-06-19T20:49:49.328Z] SSH_CONNECTION=78.47.239.97 53690 172.17.0.5 22
[2025-06-19T20:49:49.328Z] WORKSPACE_TMP=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux@tmp
[2025-06-19T20:49:49.328Z] PARALLEL=Dynamic
[2025-06-19T20:49:49.328Z] JOBSTARTTIME=Thu, 19 Jun 2025 20:49:44 +0000
[2025-06-19T20:49:49.328Z] DYNAMIC_COMPILE=false
[2025-06-19T20:49:49.328Z] RERUN_ITERATIONS=1
Did you forget the `def` keyword? Script1 seems to be setting a field named CUSTOMIZED_SDK_URL_OPTION (to a value of type String) which could lead to memory leaks or other issues.
[Pipeline] timeout
[2025-06-19T20:49:49.721Z] Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] dir
[2025-06-19T20:49:49.733Z] Running in /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary
[Pipeline] {
[Pipeline] copyArtifacts
[2025-06-19T20:50:21.097Z] Copied 5 artifacts from "build-scripts » jobs » jdk8u » jdk8u-linux-arm-temurin" build number 484
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // timeout
Did you forget the `def` keyword? Script1 seems to be setting a field named OPENJ9_REPO_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named OPENJ9_BRANCH_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named TKG_REPO_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named TKG_BRANCH_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named OPENJ9_SHA_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named CLONE_OPENJ9_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named CLONE_OPENJ9_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named JDK_VERSION_OPTION (to a value of type GStringImpl) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named JDK_IMPL_OPTION (to a value of type GStringImpl) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named TKG_REPO_OPTION (to a value of type GStringImpl) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named TKG_BRANCH_OPTION (to a value of type GStringImpl) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named VENDOR_TEST_REPOS (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named VENDOR_TEST_BRANCHES (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named VENDOR_TEST_DIRS (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named VENDOR_TEST_SHAS (to a value of type String) which could lead to memory leaks or other issues.
[Pipeline] echo
[2025-06-19T20:50:21.336Z] IS_SVT_TESTREPO is set to false
Did you forget the `def` keyword? Script1 seems to be setting a field named TEST_IMAGES_REQUIRED (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named DEBUG_IMAGES_REQUIRED (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named CODE_COVERAGE_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named ADDITIONAL_ARTIFACTS_REQUIRED_OPTION (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named CURL_OPTS (to a value of type String) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named GET_SH_CMD (to a value of type GStringImpl) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named RESOLVED_MAKE (to a value of type String) which could lead to memory leaks or other issues.
[Pipeline] dir
[2025-06-19T20:50:21.341Z] Running in /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux
[Pipeline] {
[Pipeline] sshagent
[2025-06-19T20:50:21.429Z] $ ssh-agent
[2025-06-19T20:50:22.013Z] SSH_AUTH_SOCK=/tmp/ssh-JJEIXKxryY6B/agent.433484
[2025-06-19T20:50:22.013Z] SSH_AGENT_PID=433486
[2025-06-19T20:50:22.013Z] [ssh-agent] Started.
[Pipeline] {
[Pipeline] dir
[2025-06-19T20:50:22.033Z] Running in /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests
[Pipeline] {
[Pipeline] withCredentials
[2025-06-19T20:50:22.065Z] Masking supported pattern matches of $USERNAME or $PASSWORD
[Pipeline] {
[Pipeline] sh
[2025-06-19T20:50:23.497Z] + pwd
[2025-06-19T20:50:23.497Z] + ./get.sh -s /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/.. -p arm_linux -r upstream -j 8 -i hotspot --clone_openj9 false --tkg_repo https://github.com/adoptium/TKG.git --tkg_branch master
[2025-06-19T20:50:23.498Z] TESTDIR: /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests
[2025-06-19T20:50:23.498Z] get jdk binary...
[2025-06-19T20:50:23.498Z] --sdkdir is set to upstream. Therefore, skip download jdk binary
[2025-06-19T20:50:23.498Z] Uncompressing file: OpenJDK8U-jdk_arm_linux_hotspot_8u462b05-ea.tar.gz ...
[2025-06-19T20:50:25.068Z] List files in jdkbinary folder...
[2025-06-19T20:50:25.068Z] total 224348
[2025-06-19T20:50:25.068Z] -rw-r--r-- 1 jenkins jenkins 92439141 Jun 19 20:27 OpenJDK8U-debugimage_arm_linux_hotspot_8u462b05-ea.tar.gz
[2025-06-19T20:50:25.068Z] -rw-r--r-- 1 jenkins jenkins 98384505 Jun 19 20:27 OpenJDK8U-jdk_arm_linux_hotspot_8u462b05-ea.tar.gz
[2025-06-19T20:50:25.068Z] -rw-r--r-- 1 jenkins jenkins 38799932 Jun 19 20:27 OpenJDK8U-jre_arm_linux_hotspot_8u462b05-ea.tar.gz
[2025-06-19T20:50:25.068Z] -rw-rw-r-- 1 jenkins jenkins 22020 Jun 19 20:38 OpenJDK8U-sbom_arm_linux_hotspot_8u462b05-ea-metadata.json
[2025-06-19T20:50:25.068Z] -rw-r--r-- 1 jenkins jenkins 77624 Jun 19 20:40 OpenJDK8U-sbom_arm_linux_hotspot_8u462b05-ea.json
[2025-06-19T20:50:25.068Z] drwxrwxr-x 1 jenkins jenkins 58 Jun 19 20:50 tmp
[2025-06-19T20:50:25.068Z] List files in jdkbinary/tmp folder...
[2025-06-19T20:50:25.068Z] total 0
[2025-06-19T20:50:25.068Z] drwxr-xr-x 1 jenkins jenkins 176 Jun 19 20:27 jdk8u462-b05-aarch32-20250716
[2025-06-19T20:50:25.068Z] Moving directory jdk8u462-b05-aarch32-20250716/ to ../j2sdk-image
[2025-06-19T20:50:25.068Z] Uncompressing file: OpenJDK8U-jre_arm_linux_hotspot_8u462b05-ea.tar.gz ...
[2025-06-19T20:50:25.827Z] List files in jdkbinary folder...
[2025-06-19T20:50:25.827Z] total 224348
[2025-06-19T20:50:25.827Z] -rw-r--r-- 1 jenkins jenkins 92439141 Jun 19 20:27 OpenJDK8U-debugimage_arm_linux_hotspot_8u462b05-ea.tar.gz
[2025-06-19T20:50:25.827Z] -rw-r--r-- 1 jenkins jenkins 98384505 Jun 19 20:27 OpenJDK8U-jdk_arm_linux_hotspot_8u462b05-ea.tar.gz
[2025-06-19T20:50:25.827Z] -rw-r--r-- 1 jenkins jenkins 38799932 Jun 19 20:27 OpenJDK8U-jre_arm_linux_hotspot_8u462b05-ea.tar.gz
[2025-06-19T20:50:25.827Z] -rw-rw-r-- 1 jenkins jenkins 22020 Jun 19 20:38 OpenJDK8U-sbom_arm_linux_hotspot_8u462b05-ea-metadata.json
[2025-06-19T20:50:25.827Z] -rw-r--r-- 1 jenkins jenkins 77624 Jun 19 20:40 OpenJDK8U-sbom_arm_linux_hotspot_8u462b05-ea.json
[2025-06-19T20:50:25.828Z] drwxr-xr-x 1 jenkins jenkins 176 Jun 19 20:27 j2sdk-image
[2025-06-19T20:50:25.828Z] drwxrwxr-x 1 jenkins jenkins 66 Jun 19 20:50 tmp
[2025-06-19T20:50:25.828Z] List files in jdkbinary/tmp folder...
[2025-06-19T20:50:25.828Z] total 0
[2025-06-19T20:50:25.828Z] drwxr-xr-x 1 jenkins jenkins 130 Jun 19 20:27 jdk8u462-b05-aarch32-20250716-jre
[2025-06-19T20:50:25.828Z] Moving directory jdk8u462-b05-aarch32-20250716-jre/ to ../j2re-image
[2025-06-19T20:50:25.828Z] Uncompressing OpenJDK8U-debugimage_arm_linux_hotspot_8u462b05-ea.tar.gz over ./j2sdk-image/jre...
[2025-06-19T20:50:28.305Z] Removing top-level folder jdk8u462-b05-aarch32-20250716-debug-image/
[2025-06-19T20:50:28.305Z] Removing top-level folder jdk8u462-b05-aarch32-20250716/
[2025-06-19T20:50:28.305Z] Run /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image/bin/java -version
[2025-06-19T20:50:28.305Z] =JAVA VERSION OUTPUT BEGIN=
[2025-06-19T20:50:28.305Z] openjdk version "1.8.0_462-beta"
[2025-06-19T20:50:28.305Z] OpenJDK Runtime Environment (Temurin)(build 1.8.0_462-beta-202506192012-b05)
[2025-06-19T20:50:28.305Z] OpenJDK Client VM (Temurin)(build 25.462-b05, mixed mode)
[2025-06-19T20:50:28.305Z] =JAVA VERSION OUTPUT END=
[2025-06-19T20:50:28.305Z] =RELEASE INFO BEGIN=
[2025-06-19T20:50:28.305Z] JAVA_VERSION="1.8.0_462"
[2025-06-19T20:50:28.305Z] OS_NAME="Linux"
[2025-06-19T20:50:28.305Z] OS_VERSION="2.6"
[2025-06-19T20:50:28.305Z] OS_ARCH="aarch32"
[2025-06-19T20:50:28.305Z] SOURCE=".:git:4cae973bddd7+"
[2025-06-19T20:50:28.305Z] IMPLEMENTOR="Eclipse Adoptium"
[2025-06-19T20:50:28.305Z] BUILD_SOURCE="git:5ec7cf95adce133a225cf1832d4b4915130b6a2a"
[2025-06-19T20:50:28.305Z] BUILD_SOURCE_REPO="https://github.com/adoptium/temurin-build.git"
[2025-06-19T20:50:28.305Z] SOURCE_REPO="https://github.com/adoptium/aarch32-jdk8u.git"
[2025-06-19T20:50:28.305Z] FULL_VERSION="1.8.0_462-beta-202506192012-b05"
[2025-06-19T20:50:28.305Z] SEMANTIC_VERSION="8.0.462+5"
[2025-06-19T20:50:28.305Z] BUILD_INFO="OS: Linux Version: 5.15.0-131-generic"
[2025-06-19T20:50:28.305Z] JVM_VARIANT="Hotspot"
[2025-06-19T20:50:28.305Z] JVM_VERSION="25.462-b05"
[2025-06-19T20:50:28.305Z] IMAGE_TYPE="JDK"
[2025-06-19T20:50:28.305Z] =RELEASE INFO END=
[2025-06-19T20:50:28.305Z] get testKitGen...
[2025-06-19T20:50:28.305Z] git clone -q https://github.com/adoptium/TKG.git
[2025-06-19T20:50:29.068Z] git rev-parse master
[2025-06-19T20:50:29.068Z] git checkout -q -f 1828e310fd8fb3115fde605c41aea434b90143d0
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[2025-06-19T20:50:29.581Z] $ ssh-agent -k
[2025-06-19T20:50:29.586Z] unset SSH_AUTH_SOCK;
[2025-06-19T20:50:29.586Z] unset SSH_AGENT_PID;
[2025-06-19T20:50:29.586Z] echo Agent pid 433486 killed;
[2025-06-19T20:50:30.165Z] [ssh-agent] Stopped.
[Pipeline] // sshagent
[Pipeline] fileExists
[Pipeline] }
[Pipeline] // dir
[Pipeline] }
[Pipeline] // stage
[Pipeline] echo
[2025-06-19T20:50:30.670Z] Rerun in Grinder: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=sanity.system&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=arm_linux&GENERATE_JOBS=true&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=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=8&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faarch32-jdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-linux-arm-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=&TEST_TIME=120&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=false&BUILD_LIST=system&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=484&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None
[Pipeline] echo
[2025-06-19T20:50:30.680Z] Rerun in Grinder on same machine: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=sanity.system&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=arm_linux&GENERATE_JOBS=true&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=test-docker-ubuntu2404-armv7-7&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=master&LIGHT_WEIGHT_CHECKOUT=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=8&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faarch32-jdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-linux-arm-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=&TEST_TIME=120&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=false&BUILD_LIST=system&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=484&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None
[Pipeline] stage
[Pipeline] { (setupParallelEnv)
Did you forget the `def` keyword? Script1 seems to be setting a field named parallel_tests (to a value of type LinkedHashMap) which could lead to memory leaks or other issues.
[Pipeline] timeout
[2025-06-19T20:50:30.726Z] Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] copyArtifacts
[2025-06-19T20:50:31.522Z] Copied 1 artifact from "getTRSSOutput" build number 1808
[Pipeline] sh
[2025-06-19T20:50:32.954Z] + cd ./aqa-tests/TKG/resources/TRSS
[2025-06-19T20:50:32.954Z] + tar xof -
[2025-06-19T20:50:32.954Z] + gzip -cd TRSSOutput.tar.gz
[2025-06-19T20:50:32.954Z] + rm TRSSOutput.tar.gz
[Pipeline] }
[Pipeline] // timeout
[Pipeline] timeout
[2025-06-19T20:50:33.371Z] Timeout set to expire in 20 min
[Pipeline] {
[Pipeline] echo
[2025-06-19T20:50:33.388Z] Custom URL: https://ci.adoptium.net//job/test.getDependency/lastSuccessfulBuild/artifact/
[Pipeline] sh
[2025-06-19T20:50:34.813Z] + perl ./aqa-tests/TKG/scripts/getDependencies.pl -path /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib -task default -customUrl https://ci.adoptium.net//job/test.getDependency/lastSuccessfulBuild/artifact/
[2025-06-19T20:50:34.813Z] --------------------------------------------
[2025-06-19T20:50:34.813Z] path is set to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:34.813Z] task is set to default
[2025-06-19T20:50:34.813Z] dependencyList is set to all
[2025-06-19T20:50:34.813Z] --------------------------------------------
[2025-06-19T20:50:34.813Z] Starting download third party dependent jars
[2025-06-19T20:50:34.813Z] --------------------------------------------
[2025-06-19T20:50:34.813Z] downloading dependent third party jars to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/junit/hamcrest-core.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/json-simple.jar exists with correct hash, not downloading
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/mauve/mauve.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/tools/tools.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/asm/asm.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/junit/junit.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/cvsclient/org-netbeans-lib-cvsclient.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/log4j/log4j-api.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/jcstress-tests-all-20240222.jar exists with correct hash, not downloading
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/log4j/log4j-core.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/apache-ant/lib/ant-launcher.jar exists, not downloading.
[2025-06-19T20:50:34.813Z] downloaded dependent third party jars successfully
[Pipeline] }
[Pipeline] // timeout
[Pipeline] nodesByLabel
[2025-06-19T20:50:35.237Z] Found a total of 8 nodes with the 'ci.role.test&&sw.os.linux&&hw.arch.aarch32' label
[Pipeline] sh
[2025-06-19T20:50:36.814Z] + cd ./aqa-tests/TKG
[2025-06-19T20:50:36.814Z] + uname
[2025-06-19T20:50:36.814Z] + [ Linux = AIX ]
[2025-06-19T20:50:36.814Z] + uname
[2025-06-19T20:50:36.814Z] + [ Linux = SunOS ]
[2025-06-19T20:50:36.814Z] + uname
[2025-06-19T20:50:36.814Z] + [ Linux = *BSD ]
[2025-06-19T20:50:36.814Z] + MAKE=make
[2025-06-19T20:50:36.814Z] + make genParallelList TEST=sanity.system TEST_TIME=120 NUM_MACHINES=
[2025-06-19T20:50:36.814Z] JAVA_HOME is set to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image
[2025-06-19T20:50:36.814Z] LIB_DIR is set to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:36.814Z] rm -f -r /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation; \
[2025-06-19T20:50:36.814Z] mkdir -p /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation; \
[2025-06-19T20:50:36.815Z] (ant -f ./scripts/build_tools.xml "-DTEST_JDK_HOME=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image" "-DTEST_ROOT=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/.." "-DLIB_DIR=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib" 2>&1; echo $? ) | tee "/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation/compilation.log"; \
[2025-06-19T20:50:36.815Z] if [ -z "$(tail -1 /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation/compilation.log | grep 0)" ]; then perl scripts/moveDmp.pl --compileLogPath="/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation/compilation.log" --testRoot="/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/.."; false; else rm -f -r "/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation"; fi
[2025-06-19T20:50:36.815Z] Buildfile: /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/scripts/build_tools.xml
[2025-06-19T20:50:36.815Z]
[2025-06-19T20:50:36.815Z] build:
[2025-06-19T20:50:36.815Z]
[2025-06-19T20:50:36.815Z] clean:
[2025-06-19T20:50:36.815Z]
[2025-06-19T20:50:36.815Z] init:
[2025-06-19T20:50:36.815Z] [mkdir] Created dir: /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/bin
[2025-06-19T20:50:36.815Z]
[2025-06-19T20:50:36.815Z] getDependentLibs:
[2025-06-19T20:50:37.575Z] [exec] --------------------------------------------
[2025-06-19T20:50:37.575Z] [exec] path is set to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:37.575Z] [exec] task is set to default
[2025-06-19T20:50:37.575Z] [exec] dependencyList is set to json_simple
[2025-06-19T20:50:37.575Z] [exec] --------------------------------------------
[2025-06-19T20:50:37.575Z] [exec] Starting download third party dependent jars
[2025-06-19T20:50:37.575Z] [exec] --------------------------------------------
[2025-06-19T20:50:37.575Z] [exec] downloading dependent third party jars to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:37.575Z] [exec] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/json-simple.jar exists with correct hash, not downloading
[2025-06-19T20:50:37.575Z] [exec] downloaded dependent third party jars successfully
[2025-06-19T20:50:37.575Z]
[2025-06-19T20:50:37.575Z] compile:
[2025-06-19T20:50:37.575Z] [echo] Ant version is Apache Ant(TM) version 1.10.15 compiled on August 25 2024
[2025-06-19T20:50:37.575Z] [echo] ============COMPILER SETTINGS============
[2025-06-19T20:50:37.575Z] [echo] ===fork: yes
[2025-06-19T20:50:37.575Z] [echo] ===debug: on
[2025-06-19T20:50:37.575Z] [javac] Compiling 28 source files to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/bin
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] dist:
[2025-06-19T20:50:39.147Z] [jar] Building jar: /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/bin/TestKitGen.jar
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] BUILD SUCCESSFUL
[2025-06-19T20:50:39.147Z] Total time: 2 seconds
[2025-06-19T20:50:39.147Z] 0
[2025-06-19T20:50:39.147Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image/bin/java -cp ./bin/TestKitGen.jar org.openj9.envInfo.EnvDetector
[2025-06-19T20:50:39.147Z] Unfamiliar microArch detected in TKG. It will not be added in TKG microArch!
[2025-06-19T20:50:39.147Z] microArchOutput:
[2025-06-19T20:50:39.147Z] ****************************** MACHINE INFO ******************************
[2025-06-19T20:50:39.147Z] File path : /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG
[2025-06-19T20:50:39.147Z] Free Physical Memory Size : 5273640960
[2025-06-19T20:50:39.147Z] Free space (bytes) : 645215690752
[2025-06-19T20:50:39.147Z] Total Physical Memory Size : 6442450944
[2025-06-19T20:50:39.147Z] Total space (bytes) : 960196055040
[2025-06-19T20:50:39.147Z] Usable space (bytes) : 630010515456
[2025-06-19T20:50:39.147Z] antVersion : Apache Ant(TM) version 1.10.15 compiled on August 25 2024
[2025-06-19T20:50:39.147Z] bashVersion :
[2025-06-19T20:50:39.147Z] GNU bash, version 5.2.21(1)-release (arm-unknown-linux-gnueabihf)
[2025-06-19T20:50:39.147Z] Copyright (C) 2022 Free Software Foundation, Inc.
[2025-06-19T20:50:39.147Z] License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] This is free software; you are free to change and redistribute it.
[2025-06-19T20:50:39.147Z] There is NO WARRANTY, to the extent permitted by law.
[2025-06-19T20:50:39.147Z] cpuCores : 160
[2025-06-19T20:50:39.147Z] curlVersion :
[2025-06-19T20:50:39.147Z] curl 8.5.0 (arm-unknown-linux-gnueabihf) libcurl/8.5.0 OpenSSL/3.0.13 zlib/1.3 brotli/1.1.0 zstd/1.5.5 libidn2/2.3.7 libpsl/0.21.2 (+libidn2/2.3.7) libssh/0.10.6/openssl/zlib nghttp2/1.59.0 librtmp/2.3 OpenLDAP/2.6.7
[2025-06-19T20:50:39.147Z] Release-Date: 2023-12-06, security patched: 8.5.0-2ubuntu10.6
[2025-06-19T20:50:39.147Z] Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
[2025-06-19T20:50:39.147Z] Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd
[2025-06-19T20:50:39.147Z] dockerVersion : bash: line 1: docker: command not found
[2025-06-19T20:50:39.147Z] gcc version : 13
[2025-06-19T20:50:39.147Z] gclibc version : ldd (Ubuntu GLIBC 2.39-0ubuntu8.4) 2.39
[2025-06-19T20:50:39.147Z] gdb version : bash: line 1: gdb: command not found
[2025-06-19T20:50:39.147Z] lldb version : Command could not be executed
[2025-06-19T20:50:39.147Z] makeVersion :
[2025-06-19T20:50:39.147Z] GNU Make 4.3
[2025-06-19T20:50:39.147Z] Built for arm-unknown-linux-gnueabihf
[2025-06-19T20:50:39.147Z] Copyright (C) 1988-2020 Free Software Foundation, Inc.
[2025-06-19T20:50:39.147Z] License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[2025-06-19T20:50:39.147Z] This is free software: you are free to change and redistribute it.
[2025-06-19T20:50:39.147Z] There is NO WARRANTY, to the extent permitted by law.
[2025-06-19T20:50:39.147Z] mavenVersion : bash: line 1: mvn: command not found
[2025-06-19T20:50:39.147Z] osInfo :
[2025-06-19T20:50:39.147Z] PRETTY_NAME="Ubuntu 24.04.2 LTS"
[2025-06-19T20:50:39.147Z] NAME="Ubuntu"
[2025-06-19T20:50:39.147Z] VERSION_ID="24.04"
[2025-06-19T20:50:39.147Z] VERSION="24.04.2 LTS (Noble Numbat)"
[2025-06-19T20:50:39.147Z] VERSION_CODENAME=noble
[2025-06-19T20:50:39.147Z] ID=ubuntu
[2025-06-19T20:50:39.147Z] ID_LIKE=debian
[2025-06-19T20:50:39.147Z] HOME_URL="https://www.ubuntu.com/"
[2025-06-19T20:50:39.147Z] SUPPORT_URL="https://help.ubuntu.com/"
[2025-06-19T20:50:39.147Z] BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
[2025-06-19T20:50:39.147Z] PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
[2025-06-19T20:50:39.147Z] UBUNTU_CODENAME=noble
[2025-06-19T20:50:39.147Z] LOGO=ubuntu-logo
[2025-06-19T20:50:39.147Z] osLabel : ubuntu.24
[2025-06-19T20:50:39.147Z] perlVersion :
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] This is perl 5, version 38, subversion 2 (v5.38.2) built for arm-linux-gnueabihf-thread-multi-64int
[2025-06-19T20:50:39.147Z] (with 45 registered patches, see perl -V for more detail)
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] Copyright 1987-2023, Larry Wall
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] Perl may be copied only under the terms of either the Artistic License or the
[2025-06-19T20:50:39.147Z] GNU General Public License, which may be found in the Perl 5 source kit.
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] Complete documentation for Perl, including FAQ lists, should be found on
[2025-06-19T20:50:39.147Z] this system using "man perl" or "perldoc perl". If you have access to the
[2025-06-19T20:50:39.147Z] Internet, point your browser at https://www.perl.org/, the Perl Home Page.
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] podmanVersion : bash: line 1: podman: command not found
[2025-06-19T20:50:39.147Z] procArch : aarch64
[2025-06-19T20:50:39.147Z] sysArch : aarch64
[2025-06-19T20:50:39.147Z] sysOS : Linux
[2025-06-19T20:50:39.147Z] ulimit :
[2025-06-19T20:50:39.147Z] real-time non-blocking time (microseconds, -R) unlimited
[2025-06-19T20:50:39.147Z] core file size (blocks, -c) unlimited
[2025-06-19T20:50:39.147Z] data seg size (kbytes, -d) unlimited
[2025-06-19T20:50:39.147Z] scheduling priority (-e) 0
[2025-06-19T20:50:39.147Z] file size (blocks, -f) unlimited
[2025-06-19T20:50:39.147Z] pending signals (-i) 2053826
[2025-06-19T20:50:39.147Z] max locked memory (kbytes, -l) 64
[2025-06-19T20:50:39.147Z] max memory size (kbytes, -m) unlimited
[2025-06-19T20:50:39.147Z] open files (-n) 1048576
[2025-06-19T20:50:39.147Z] pipe size (512 bytes, -p) 8
[2025-06-19T20:50:39.147Z] POSIX message queues (bytes, -q) 819200
[2025-06-19T20:50:39.147Z] real-time priority (-r) 0
[2025-06-19T20:50:39.147Z] stack size (kbytes, -s) 8192
[2025-06-19T20:50:39.147Z] cpu time (seconds, -t) unlimited
[2025-06-19T20:50:39.147Z] max user processes (-u) unlimited
[2025-06-19T20:50:39.147Z] virtual memory (kbytes, -v) unlimited
[2025-06-19T20:50:39.147Z] file locks (-x) unlimited
[2025-06-19T20:50:39.147Z] uname : Linux 29e2b6d59b25 5.15.0-131-generic #141-Ubuntu SMP Fri Jan 10 21:25:15 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
[2025-06-19T20:50:39.147Z] vmVendor : Oracle Corporation
[2025-06-19T20:50:39.147Z] vmVersion : 25.462-b05
[2025-06-19T20:50:39.147Z] xlc version : bash: line 1: xlC: command not found
[2025-06-19T20:50:39.147Z] **************************************************************************
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] System.getProperty('java.vm.name')=OpenJDK Client VM
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] System.getProperty('java.vendor')=Temurin
[2025-06-19T20:50:39.147Z]
[2025-06-19T20:50:39.147Z] System.getProperty('os.name')=Linux
[2025-06-19T20:50:39.148Z]
[2025-06-19T20:50:39.148Z] System.getProperty('os.arch')=arm
[2025-06-19T20:50:39.148Z]
[2025-06-19T20:50:39.148Z] System.getProperty('java.fullversion')=null
[2025-06-19T20:50:39.148Z]
[2025-06-19T20:50:39.148Z] System.getProperty('sun.arch.data.model')=32
[2025-06-19T20:50:39.148Z]
[2025-06-19T20:50:39.907Z] make -f makeGen.mk AUTO_DETECT=true MODE=parallelList NUM_MACHINES= TEST_TIME=120 TESTTARGET=sanity.system TESTLIST= TRSS_URL= LIB_DIR=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:39.907Z] make[1]: Entering directory '/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG'
[2025-06-19T20:50:39.907Z] perl scripts/configure.pl
[2025-06-19T20:50:39.907Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image/bin/java -cp "./bin/TestKitGen.jar:/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/json-simple.jar" org.testKitGen.MainRunner --mode=parallelList --spec=linux_arm --microArch="" --osLabel="ubuntu.24" --jdkVersion=8 --impl=hotspot --vendor="temurin" --buildList=system --iterations=1 --aotIterations= --testFlag= --testTarget=sanity.system --testList= --numOfMachines= --testTime=120 --TRSSURL=
[2025-06-19T20:50:39.907Z] Modes data parsed from resources/modes.xml and resources/ottawa.csv.
[2025-06-19T20:50:39.907Z]
[2025-06-19T20:50:39.907Z]
[2025-06-19T20:50:39.907Z] Starting to generate parallel test lists.
[2025-06-19T20:50:39.907Z]
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/churn/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/daaLoadTest/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/jcstress/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/jlm/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/lambdaLoadTest/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/mathLoadTest/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/mauveLoadTest/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/modularity/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/otherLoadTest/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/security/playlist.xml
[2025-06-19T20:50:39.907Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/sharedClasses/playlist.xml
[2025-06-19T20:50:39.907Z] Attempting to get test duration data from TRSS.
[2025-06-19T20:50:39.907Z] curl --silent --max-time 120 -L -k https://trss.adoptopenjdk.net/api/getTestAvgDuration?limit=10&jdkVersion=8&impl=hs&platform=arm_linux&group=system&level=sanity
[2025-06-19T20:50:40.666Z] Attempting to get test duration data from cached files.
[2025-06-19T20:50:40.666Z]
[2025-06-19T20:50:40.666Z] TEST DURATION
[2025-06-19T20:50:40.666Z] ====================================================================================
[2025-06-19T20:50:40.666Z] Total number of tests searched: 51
[2025-06-19T20:50:40.666Z] Number of test durations found: 51
[2025-06-19T20:50:40.666Z] Top slowest tests:
[2025-06-19T20:50:40.666Z] 15m45s TestJlmRemoteThreadAuth_2
[2025-06-19T20:50:40.666Z] 13m06s TestJlmRemoteThreadNoAuth_2
[2025-06-19T20:50:40.666Z] 11m49s TestJlmRemoteClassAuth_2
[2025-06-19T20:50:40.666Z] ====================================================================================
[2025-06-19T20:50:40.666Z]
[2025-06-19T20:50:40.666Z] Test target is split into 1 lists.
[2025-06-19T20:50:40.666Z] Reducing estimated test running time from 79m14s to 79m14s.
[2025-06-19T20:50:40.666Z]
[2025-06-19T20:50:40.666Z] -------------------------------------testList_0-------------------------------------
[2025-06-19T20:50:40.666Z] Number of tests: 51
[2025-06-19T20:50:40.666Z] Estimated running time: 79m14s
[2025-06-19T20:50:40.666Z] TESTLIST=TestJlmRemoteThreadAuth_2,TestJlmRemoteThreadNoAuth_2,TestJlmRemoteClassAuth_2,MauveSingleThrdLoad_HS_5m_2,MathLoadTest_bigdecimal_5m_2,MauveSingleInvocLoad_HS_5m_2,ClassLoadingTest_5m_2,LambdaLoadTest_HS_5m_2,MauveMultiThrdLoad_5m_2,MathLoadTest_autosimd_5m_2,TestJlmRemoteNotifierProxyAuth_2,ParallelStreamsLoadTest_HS_2,TestJlmLocal_1,TestJlmRemoteMemoryNoAuth_2,TestJlmRemoteMemoryAuth_1,TestJlmRemoteClassNoAuth_2,TestJlmRemoteMemoryNoAuth_0,TestJlmRemoteClassNoAuth_0,MathLoadTest_bigdecimal_5m_0,TestJlmRemoteMemoryAuth_2,TestJlmRemoteMemoryAuth_0,TestJlmRemoteClassNoAuth_1,MauveSingleThrdLoad_HS_5m_0,TestJlmRemoteThreadNoAuth_1,TestJlmRemoteThreadAuth_1,ParallelStreamsLoadTest_HS_1,MathLoadTest_autosimd_5m_0,LambdaLoadTest_HS_5m_0,TestJlmRemoteNotifierProxyAuth_1,TestJlmLocal_2,TestJlmLocal_0,TestJlmRemoteMemoryNoAuth_1,TestJlmRemoteClassAuth_0,NioLoadTest_5m_0,MauveMultiThrdLoad_5m_0,TestJlmRemoteThreadAuth_0,NioLoadTest_5m_1,MathLoadTest_autosimd_5m_1,ClassLoadingTest_5m_1,MauveSingleInvocLoad_HS_5m_0,ParallelStreamsLoadTest_HS_0,MauveSingleThrdLoad_HS_5m_1,MathLoadTest_bigdecimal_5m_1,LambdaLoadTest_HS_5m_1,TestJlmRemoteThreadNoAuth_0,NioLoadTest_5m_2,MauveSingleInvocLoad_HS_5m_1,MauveMultiThrdLoad_5m_1,ClassLoadingTest_5m_0,TestJlmRemoteNotifierProxyAuth_0,TestJlmRemoteClassAuth_1
[2025-06-19T20:50:40.666Z] ------------------------------------------------------------------------------------
[2025-06-19T20:50:40.666Z]
[2025-06-19T20:50:40.666Z] Parallel test lists file (/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/parallelList.mk) is generated successfully.
[2025-06-19T20:50:40.666Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG'
[Pipeline] fileExists
[Pipeline] echo
[2025-06-19T20:50:41.185Z] read parallelList.mk file: aqa-tests/TKG/parallelList.mk
[Pipeline] readProperties
[Pipeline] echo
[2025-06-19T20:50:41.581Z] NUM_LIST=1, Fall back to regenerate parallel lists with NUM_MACHINES=3.
[Pipeline] sh
[2025-06-19T20:50:43.006Z] + cd ./aqa-tests/TKG
[2025-06-19T20:50:43.006Z] + uname
[2025-06-19T20:50:43.006Z] + [ Linux = AIX ]
[2025-06-19T20:50:43.006Z] + uname
[2025-06-19T20:50:43.006Z] + [ Linux = SunOS ]
[2025-06-19T20:50:43.006Z] + uname
[2025-06-19T20:50:43.006Z] + [ Linux = *BSD ]
[2025-06-19T20:50:43.006Z] + MAKE=make
[2025-06-19T20:50:43.006Z] + make genParallelList TEST=sanity.system NUM_MACHINES=3 TEST_TIME=
[2025-06-19T20:50:43.006Z] JAVA_HOME is set to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image
[2025-06-19T20:50:43.006Z] LIB_DIR is set to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:43.006Z] rm -f -r /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation; \
[2025-06-19T20:50:43.006Z] mkdir -p /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation; \
[2025-06-19T20:50:43.006Z] (ant -f ./scripts/build_tools.xml "-DTEST_JDK_HOME=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image" "-DTEST_ROOT=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/.." "-DLIB_DIR=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib" 2>&1; echo $? ) | tee "/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation/compilation.log"; \
[2025-06-19T20:50:43.006Z] if [ -z "$(tail -1 /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation/compilation.log | grep 0)" ]; then perl scripts/moveDmp.pl --compileLogPath="/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation/compilation.log" --testRoot="/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/.."; false; else rm -f -r "/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/output_compilation"; fi
[2025-06-19T20:50:43.006Z] Buildfile: /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/scripts/build_tools.xml
[2025-06-19T20:50:43.006Z]
[2025-06-19T20:50:43.006Z] build:
[2025-06-19T20:50:43.006Z]
[2025-06-19T20:50:43.006Z] clean:
[2025-06-19T20:50:43.006Z] [delete] Deleting: /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/autoGenEnv.mk
[2025-06-19T20:50:43.006Z] [delete] Deleting directory /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/bin
[2025-06-19T20:50:43.006Z]
[2025-06-19T20:50:43.006Z] init:
[2025-06-19T20:50:43.006Z] [mkdir] Created dir: /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/bin
[2025-06-19T20:50:43.006Z]
[2025-06-19T20:50:43.006Z] getDependentLibs:
[2025-06-19T20:50:43.773Z] [exec] --------------------------------------------
[2025-06-19T20:50:43.773Z] [exec] path is set to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:43.773Z] [exec] task is set to default
[2025-06-19T20:50:43.773Z] [exec] dependencyList is set to json_simple
[2025-06-19T20:50:43.773Z] [exec] --------------------------------------------
[2025-06-19T20:50:43.773Z] [exec] Starting download third party dependent jars
[2025-06-19T20:50:43.773Z] [exec] --------------------------------------------
[2025-06-19T20:50:43.773Z] [exec] downloading dependent third party jars to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:43.773Z] [exec] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/json-simple.jar exists with correct hash, not downloading
[2025-06-19T20:50:43.773Z] [exec] downloaded dependent third party jars successfully
[2025-06-19T20:50:43.773Z]
[2025-06-19T20:50:43.773Z] compile:
[2025-06-19T20:50:43.773Z] [echo] Ant version is Apache Ant(TM) version 1.10.15 compiled on August 25 2024
[2025-06-19T20:50:43.773Z] [echo] ============COMPILER SETTINGS============
[2025-06-19T20:50:43.773Z] [echo] ===fork: yes
[2025-06-19T20:50:43.773Z] [echo] ===debug: on
[2025-06-19T20:50:43.773Z] [javac] Compiling 28 source files to /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/bin
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] dist:
[2025-06-19T20:50:45.350Z] [jar] Building jar: /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/bin/TestKitGen.jar
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] BUILD SUCCESSFUL
[2025-06-19T20:50:45.350Z] Total time: 2 seconds
[2025-06-19T20:50:45.350Z] 0
[2025-06-19T20:50:45.350Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image/bin/java -cp ./bin/TestKitGen.jar org.openj9.envInfo.EnvDetector
[2025-06-19T20:50:45.350Z] Unfamiliar microArch detected in TKG. It will not be added in TKG microArch!
[2025-06-19T20:50:45.350Z] microArchOutput:
[2025-06-19T20:50:45.350Z] ****************************** MACHINE INFO ******************************
[2025-06-19T20:50:45.350Z] File path : /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG
[2025-06-19T20:50:45.350Z] Free Physical Memory Size : 5274058752
[2025-06-19T20:50:45.350Z] Free space (bytes) : 645215690752
[2025-06-19T20:50:45.350Z] Total Physical Memory Size : 6442450944
[2025-06-19T20:50:45.350Z] Total space (bytes) : 960196055040
[2025-06-19T20:50:45.350Z] Usable space (bytes) : 630010515456
[2025-06-19T20:50:45.350Z] antVersion : Apache Ant(TM) version 1.10.15 compiled on August 25 2024
[2025-06-19T20:50:45.350Z] bashVersion :
[2025-06-19T20:50:45.350Z] GNU bash, version 5.2.21(1)-release (arm-unknown-linux-gnueabihf)
[2025-06-19T20:50:45.350Z] Copyright (C) 2022 Free Software Foundation, Inc.
[2025-06-19T20:50:45.350Z] License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] This is free software; you are free to change and redistribute it.
[2025-06-19T20:50:45.350Z] There is NO WARRANTY, to the extent permitted by law.
[2025-06-19T20:50:45.350Z] cpuCores : 160
[2025-06-19T20:50:45.350Z] curlVersion :
[2025-06-19T20:50:45.350Z] curl 8.5.0 (arm-unknown-linux-gnueabihf) libcurl/8.5.0 OpenSSL/3.0.13 zlib/1.3 brotli/1.1.0 zstd/1.5.5 libidn2/2.3.7 libpsl/0.21.2 (+libidn2/2.3.7) libssh/0.10.6/openssl/zlib nghttp2/1.59.0 librtmp/2.3 OpenLDAP/2.6.7
[2025-06-19T20:50:45.350Z] Release-Date: 2023-12-06, security patched: 8.5.0-2ubuntu10.6
[2025-06-19T20:50:45.350Z] Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
[2025-06-19T20:50:45.350Z] Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd
[2025-06-19T20:50:45.350Z] dockerVersion : bash: line 1: docker: command not found
[2025-06-19T20:50:45.350Z] gcc version : 13
[2025-06-19T20:50:45.350Z] gclibc version : ldd (Ubuntu GLIBC 2.39-0ubuntu8.4) 2.39
[2025-06-19T20:50:45.350Z] gdb version : bash: line 1: gdb: command not found
[2025-06-19T20:50:45.350Z] lldb version : Command could not be executed
[2025-06-19T20:50:45.350Z] makeVersion :
[2025-06-19T20:50:45.350Z] GNU Make 4.3
[2025-06-19T20:50:45.350Z] Built for arm-unknown-linux-gnueabihf
[2025-06-19T20:50:45.350Z] Copyright (C) 1988-2020 Free Software Foundation, Inc.
[2025-06-19T20:50:45.350Z] License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
[2025-06-19T20:50:45.350Z] This is free software: you are free to change and redistribute it.
[2025-06-19T20:50:45.350Z] There is NO WARRANTY, to the extent permitted by law.
[2025-06-19T20:50:45.350Z] mavenVersion : bash: line 1: mvn: command not found
[2025-06-19T20:50:45.350Z] osInfo :
[2025-06-19T20:50:45.350Z] PRETTY_NAME="Ubuntu 24.04.2 LTS"
[2025-06-19T20:50:45.350Z] NAME="Ubuntu"
[2025-06-19T20:50:45.350Z] VERSION_ID="24.04"
[2025-06-19T20:50:45.350Z] VERSION="24.04.2 LTS (Noble Numbat)"
[2025-06-19T20:50:45.350Z] VERSION_CODENAME=noble
[2025-06-19T20:50:45.350Z] ID=ubuntu
[2025-06-19T20:50:45.350Z] ID_LIKE=debian
[2025-06-19T20:50:45.350Z] HOME_URL="https://www.ubuntu.com/"
[2025-06-19T20:50:45.350Z] SUPPORT_URL="https://help.ubuntu.com/"
[2025-06-19T20:50:45.350Z] BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
[2025-06-19T20:50:45.350Z] PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
[2025-06-19T20:50:45.350Z] UBUNTU_CODENAME=noble
[2025-06-19T20:50:45.350Z] LOGO=ubuntu-logo
[2025-06-19T20:50:45.350Z] osLabel : ubuntu.24
[2025-06-19T20:50:45.350Z] perlVersion :
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] This is perl 5, version 38, subversion 2 (v5.38.2) built for arm-linux-gnueabihf-thread-multi-64int
[2025-06-19T20:50:45.350Z] (with 45 registered patches, see perl -V for more detail)
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] Copyright 1987-2023, Larry Wall
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] Perl may be copied only under the terms of either the Artistic License or the
[2025-06-19T20:50:45.350Z] GNU General Public License, which may be found in the Perl 5 source kit.
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] Complete documentation for Perl, including FAQ lists, should be found on
[2025-06-19T20:50:45.350Z] this system using "man perl" or "perldoc perl". If you have access to the
[2025-06-19T20:50:45.350Z] Internet, point your browser at https://www.perl.org/, the Perl Home Page.
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] podmanVersion : bash: line 1: podman: command not found
[2025-06-19T20:50:45.350Z] procArch : aarch64
[2025-06-19T20:50:45.350Z] sysArch : aarch64
[2025-06-19T20:50:45.350Z] sysOS : Linux
[2025-06-19T20:50:45.350Z] ulimit :
[2025-06-19T20:50:45.350Z] real-time non-blocking time (microseconds, -R) unlimited
[2025-06-19T20:50:45.350Z] core file size (blocks, -c) unlimited
[2025-06-19T20:50:45.350Z] data seg size (kbytes, -d) unlimited
[2025-06-19T20:50:45.350Z] scheduling priority (-e) 0
[2025-06-19T20:50:45.350Z] file size (blocks, -f) unlimited
[2025-06-19T20:50:45.350Z] pending signals (-i) 2053826
[2025-06-19T20:50:45.350Z] max locked memory (kbytes, -l) 64
[2025-06-19T20:50:45.350Z] max memory size (kbytes, -m) unlimited
[2025-06-19T20:50:45.350Z] open files (-n) 1048576
[2025-06-19T20:50:45.350Z] pipe size (512 bytes, -p) 8
[2025-06-19T20:50:45.350Z] POSIX message queues (bytes, -q) 819200
[2025-06-19T20:50:45.350Z] real-time priority (-r) 0
[2025-06-19T20:50:45.350Z] stack size (kbytes, -s) 8192
[2025-06-19T20:50:45.350Z] cpu time (seconds, -t) unlimited
[2025-06-19T20:50:45.350Z] max user processes (-u) unlimited
[2025-06-19T20:50:45.350Z] virtual memory (kbytes, -v) unlimited
[2025-06-19T20:50:45.350Z] file locks (-x) unlimited
[2025-06-19T20:50:45.350Z] uname : Linux 29e2b6d59b25 5.15.0-131-generic #141-Ubuntu SMP Fri Jan 10 21:25:15 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
[2025-06-19T20:50:45.350Z] vmVendor : Oracle Corporation
[2025-06-19T20:50:45.350Z] vmVersion : 25.462-b05
[2025-06-19T20:50:45.350Z] xlc version : bash: line 1: xlC: command not found
[2025-06-19T20:50:45.350Z] **************************************************************************
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] System.getProperty('java.vm.name')=OpenJDK Client VM
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] System.getProperty('java.vendor')=Temurin
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] System.getProperty('os.name')=Linux
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] System.getProperty('os.arch')=arm
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] System.getProperty('java.fullversion')=null
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:45.350Z] System.getProperty('sun.arch.data.model')=32
[2025-06-19T20:50:45.350Z]
[2025-06-19T20:50:46.116Z] make -f makeGen.mk AUTO_DETECT=true MODE=parallelList NUM_MACHINES=3 TEST_TIME= TESTTARGET=sanity.system TESTLIST= TRSS_URL= LIB_DIR=/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib
[2025-06-19T20:50:46.116Z] make[1]: Entering directory '/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG'
[2025-06-19T20:50:46.116Z] perl scripts/configure.pl
[2025-06-19T20:50:46.116Z] /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/jdkbinary/j2sdk-image/bin/java -cp "./bin/TestKitGen.jar:/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/../../testDependency/system_lib/json-simple.jar" org.testKitGen.MainRunner --mode=parallelList --spec=linux_arm --microArch="" --osLabel="ubuntu.24" --jdkVersion=8 --impl=hotspot --vendor="temurin" --buildList=system --iterations=1 --aotIterations= --testFlag= --testTarget=sanity.system --testList= --numOfMachines=3 --testTime= --TRSSURL=
[2025-06-19T20:50:46.116Z] Modes data parsed from resources/modes.xml and resources/ottawa.csv.
[2025-06-19T20:50:46.116Z]
[2025-06-19T20:50:46.116Z]
[2025-06-19T20:50:46.116Z] Starting to generate parallel test lists.
[2025-06-19T20:50:46.116Z]
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/churn/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/daaLoadTest/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/jcstress/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/jlm/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/lambdaLoadTest/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/mathLoadTest/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/mauveLoadTest/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/modularity/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/otherLoadTest/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/security/playlist.xml
[2025-06-19T20:50:46.116Z] Parsing /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../system/sharedClasses/playlist.xml
[2025-06-19T20:50:46.116Z] Attempting to get test duration data from TRSS.
[2025-06-19T20:50:46.116Z] curl --silent --max-time 120 -L -k https://trss.adoptopenjdk.net/api/getTestAvgDuration?limit=10&jdkVersion=8&impl=hs&platform=arm_linux&group=system&level=sanity
[2025-06-19T20:50:46.878Z] Attempting to get test duration data from cached files.
[2025-06-19T20:50:46.878Z]
[2025-06-19T20:50:46.878Z] TEST DURATION
[2025-06-19T20:50:46.878Z] ====================================================================================
[2025-06-19T20:50:46.878Z] Total number of tests searched: 51
[2025-06-19T20:50:46.878Z] Number of test durations found: 51
[2025-06-19T20:50:46.878Z] Top slowest tests:
[2025-06-19T20:50:46.878Z] 15m45s TestJlmRemoteThreadAuth_2
[2025-06-19T20:50:46.878Z] 13m06s TestJlmRemoteThreadNoAuth_2
[2025-06-19T20:50:46.878Z] 11m49s TestJlmRemoteClassAuth_2
[2025-06-19T20:50:46.878Z] ====================================================================================
[2025-06-19T20:50:46.878Z]
[2025-06-19T20:50:46.878Z] Test target is split into 3 lists.
[2025-06-19T20:50:46.878Z] Reducing estimated test running time from 79m14s to 27m00s.
[2025-06-19T20:50:46.878Z]
[2025-06-19T20:50:46.878Z] -------------------------------------testList_0-------------------------------------
[2025-06-19T20:50:46.878Z] Number of tests: 42
[2025-06-19T20:50:46.878Z] Estimated running time: 25m54s
[2025-06-19T20:50:46.878Z] TESTLIST=TestJlmRemoteThreadAuth_2,MauveSingleInvocLoad_HS_5m_2,MauveMultiThrdLoad_5m_2,TestJlmLocal_1,TestJlmRemoteMemoryNoAuth_2,TestJlmRemoteMemoryAuth_1,TestJlmRemoteClassNoAuth_2,TestJlmRemoteMemoryNoAuth_0,TestJlmRemoteClassNoAuth_0,MathLoadTest_bigdecimal_5m_0,TestJlmRemoteMemoryAuth_2,TestJlmRemoteMemoryAuth_0,TestJlmRemoteClassNoAuth_1,MauveSingleThrdLoad_HS_5m_0,TestJlmRemoteThreadNoAuth_1,TestJlmRemoteThreadAuth_1,ParallelStreamsLoadTest_HS_1,MathLoadTest_autosimd_5m_0,LambdaLoadTest_HS_5m_0,TestJlmRemoteNotifierProxyAuth_1,TestJlmLocal_2,TestJlmLocal_0,TestJlmRemoteMemoryNoAuth_1,TestJlmRemoteClassAuth_0,NioLoadTest_5m_0,MauveMultiThrdLoad_5m_0,TestJlmRemoteThreadAuth_0,NioLoadTest_5m_1,MathLoadTest_autosimd_5m_1,ClassLoadingTest_5m_1,MauveSingleInvocLoad_HS_5m_0,ParallelStreamsLoadTest_HS_0,MauveSingleThrdLoad_HS_5m_1,MathLoadTest_bigdecimal_5m_1,LambdaLoadTest_HS_5m_1,TestJlmRemoteThreadNoAuth_0,NioLoadTest_5m_2,MauveSingleInvocLoad_HS_5m_1,MauveMultiThrdLoad_5m_1,ClassLoadingTest_5m_0,TestJlmRemoteNotifierProxyAuth_0,TestJlmRemoteClassAuth_1
[2025-06-19T20:50:46.878Z] ------------------------------------------------------------------------------------
[2025-06-19T20:50:46.878Z]
[2025-06-19T20:50:46.878Z] -------------------------------------testList_1-------------------------------------
[2025-06-19T20:50:46.878Z] Number of tests: 5
[2025-06-19T20:50:46.878Z] Estimated running time: 26m19s
[2025-06-19T20:50:46.878Z] TESTLIST=TestJlmRemoteThreadNoAuth_2,MathLoadTest_bigdecimal_5m_2,LambdaLoadTest_HS_5m_2,TestJlmRemoteNotifierProxyAuth_2,ParallelStreamsLoadTest_HS_2
[2025-06-19T20:50:46.878Z] ------------------------------------------------------------------------------------
[2025-06-19T20:50:46.878Z]
[2025-06-19T20:50:46.878Z] -------------------------------------testList_2-------------------------------------
[2025-06-19T20:50:46.878Z] Number of tests: 4
[2025-06-19T20:50:46.878Z] Estimated running time: 27m00s
[2025-06-19T20:50:46.878Z] TESTLIST=TestJlmRemoteClassAuth_2,MauveSingleThrdLoad_HS_5m_2,ClassLoadingTest_5m_2,MathLoadTest_autosimd_5m_2
[2025-06-19T20:50:46.878Z] ------------------------------------------------------------------------------------
[2025-06-19T20:50:46.878Z]
[2025-06-19T20:50:46.878Z] Parallel test lists file (/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG/../TKG/parallelList.mk) is generated successfully.
[2025-06-19T20:50:46.878Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG'
[Pipeline] fileExists
[Pipeline] echo
[2025-06-19T20:50:47.398Z] read parallelList.mk file: aqa-tests/TKG/parallelList.mk
[Pipeline] readProperties
[Pipeline] echo
[2025-06-19T20:50:47.786Z] Saving parallelList.mk file on jenkins...
[Pipeline] dir
[2025-06-19T20:50:47.788Z] Running in /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux/aqa-tests/TKG
[Pipeline] {
[Pipeline] archiveArtifacts
[2025-06-19T20:50:47.944Z] Archiving artifacts
[2025-06-19T20:50:48.201Z] Recording fingerprints
[Pipeline] }
[Pipeline] // dir
[Pipeline] echo
[2025-06-19T20:50:48.368Z] [PARALLEL: Dynamic] childJobNum is 3, creating jobs and running them in parallel...
Did you forget the `def` keyword? Script1 seems to be setting a field named create_jobs (to a value of type LinkedHashMap) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named parallelTestParams (to a value of type LinkedHashMap) which could lead to memory leaks or other issues.
[Pipeline] parallel
[Pipeline] { (Branch: testList_0)
[Pipeline] { (Branch: testList_1)
[Pipeline] { (Branch: testList_2)
[Pipeline] echo
[2025-06-19T20:50:48.956Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_sanity.system_arm_linux_testList_0 params for generating the job
[Pipeline] echo
[2025-06-19T20:50:48.958Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_sanity.system_arm_linux_testList_1 params for generating the job
[Pipeline] echo
[2025-06-19T20:50:48.959Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_sanity.system_arm_linux_testList_2 params for generating the job
[Pipeline] fileExists
[Pipeline] fileExists
[Pipeline] fileExists
[Pipeline] jobDsl
[Pipeline] jobDsl
[Pipeline] jobDsl
[2025-06-19T20:50:49.763Z] Processing DSL script aqa-tests/buildenv/jenkins/testJobTemplate
[2025-06-19T20:50:49.772Z] Processing DSL script aqa-tests/buildenv/jenkins/testJobTemplate
[2025-06-19T20:50:49.884Z] Processing DSL script aqa-tests/buildenv/jenkins/testJobTemplate
[2025-06-19T20:54:16.417Z] LEVELS: [sanity]
[2025-06-19T20:54:16.417Z] LEVELS: [sanity]
[2025-06-19T20:54:16.419Z] JDK_VERSIONS: [8]
[2025-06-19T20:54:16.420Z] JDK_VERSIONS: [8]
[2025-06-19T20:54:16.420Z] GROUPS: [system]
[2025-06-19T20:54:16.420Z] GROUPS: [system]
[2025-06-19T20:54:16.420Z] ARCH_OS_LIST: [arm_linux]
[2025-06-19T20:54:16.421Z] ARCH_OS_LIST: [arm_linux]
[2025-06-19T20:54:16.530Z] LEVELS: [sanity]
[2025-06-19T20:54:16.530Z] JDK_VERSIONS: [8]
[2025-06-19T20:54:16.530Z] GROUPS: [system]
[2025-06-19T20:54:16.530Z] ARCH_OS_LIST: [arm_linux]
[2025-06-19T20:54:16.592Z] Existing items:
[2025-06-19T20:54:16.592Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_0'}
[2025-06-19T20:54:16.592Z] Unreferenced items:
[2025-06-19T20:54:16.592Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_1'}
[2025-06-19T20:54:16.592Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_2'}
[2025-06-19T20:54:16.602Z] Existing items:
[2025-06-19T20:54:16.602Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_0'}
[2025-06-19T20:54:16.602Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_1'}
[2025-06-19T20:54:16.602Z] Unreferenced items:
[2025-06-19T20:54:16.602Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_2'}
[2025-06-19T20:54:16.627Z] Existing items:
[2025-06-19T20:54:16.627Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_0'}
[2025-06-19T20:54:16.627Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_1'}
[2025-06-19T20:54:16.627Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_2'}
[Pipeline] }
[Pipeline] }
[Pipeline] }
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] echo
[2025-06-19T20:54:18.826Z] PROCESSCATCH: Terminating any hung/left over test processes:
[Pipeline] sh
[2025-06-19T20:54:20.384Z] + aqa-tests/terminateTestProcesses.sh jenkins
[2025-06-19T20:54:20.384Z] Unix type machine..
[2025-06-19T20:54:20.384Z] Running on a Linux host
[2025-06-19T20:54:20.384Z] Woohoo - no rogue processes detected!
[Pipeline] cleanWs
[2025-06-19T20:54:21.047Z] [WS-CLEANUP] Deleting project workspace...
[2025-06-19T20:54:21.047Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration...
[2025-06-19T20:54:21.859Z] [WS-CLEANUP] done
[Pipeline] sh
[2025-06-19T20:54:23.426Z] + find /tmp -name *core* -print -exec rm -f {} ;
[Pipeline] }
[Pipeline] // timeout
[Pipeline] timeout
[2025-06-19T20:54:23.840Z] Timeout set to expire in 5 min 0 sec
[Pipeline] {
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] echo
[2025-06-19T20:54:23.940Z] SETUP_LABEL: ci.role.test
[Pipeline] stage
[Pipeline] { (Parallel Tests)
[Pipeline] parallel
[Pipeline] { (Branch: testList_0)
[Pipeline] { (Branch: testList_1)
[Pipeline] { (Branch: testList_2)
[Pipeline] build
[2025-06-19T20:54:23.973Z] Scheduling project: Test_openjdk8_hs_sanity.system_arm_linux_testList_0
[Pipeline] build
[2025-06-19T20:54:23.983Z] Scheduling project: Test_openjdk8_hs_sanity.system_arm_linux_testList_1
[Pipeline] build
[2025-06-19T20:54:23.996Z] Scheduling project: Test_openjdk8_hs_sanity.system_arm_linux_testList_2
[2025-06-19T20:54:32.775Z] Starting building: Test_openjdk8_hs_sanity.system_arm_linux_testList_0 #7
[2025-06-19T20:54:32.784Z] Starting building: Test_openjdk8_hs_sanity.system_arm_linux_testList_1 #5
[2025-06-19T20:54:32.806Z] Starting building: Test_openjdk8_hs_sanity.system_arm_linux_testList_2 #5
[2025-06-19T21:32:34.959Z] Build Test_openjdk8_hs_sanity.system_arm_linux_testList_2 #5 completed: UNSTABLE
[Pipeline] }
[2025-06-19T21:36:20.292Z] Build Test_openjdk8_hs_sanity.system_arm_linux_testList_0 #7 completed: UNSTABLE
[Pipeline] }
[2025-06-19T21:48:55.142Z] Build Test_openjdk8_hs_sanity.system_arm_linux_testList_1 #5 completed: SUCCESS
[Pipeline] }
[Pipeline] // parallel
[Pipeline] node
[2025-06-19T21:48:55.266Z] Running on test-osuosl-aix72-ppc64-5 in /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux
[Pipeline] {
[Pipeline] cleanWs
[2025-06-19T21:48:55.648Z] [WS-CLEANUP] Deleting project workspace...
[2025-06-19T21:48:55.648Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration...
[2025-06-19T21:48:55.823Z] [WS-CLEANUP] done
[Pipeline] echo
[2025-06-19T21:48:55.835Z] Test_openjdk8_hs_sanity.system_arm_linux_testList_2 #5 completed with status UNSTABLE
[Pipeline] timeout
[2025-06-19T21:48:55.839Z] Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] copyArtifacts
[2025-06-19T21:48:57.099Z] Copied 1 artifact from "Test_openjdk8_hs_sanity.system_arm_linux_testList_2" build number 5
[Pipeline] }
[Pipeline] // timeout
[Pipeline] step
[2025-06-19T21:48:57.313Z] TAP Reports Processing: START
[2025-06-19T21:48:57.314Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_sanity.system_arm_linux_testList_2/5/**/*.tap
[2025-06-19T21:48:57.488Z] Saving reports...
[2025-06-19T21:48:57.669Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_sanity.system_arm_linux/builds/463/tap-master-files/Test_openjdk8_hs_sanity.system_arm_linux_testList_2/5/aqa-tests/TKG/output_17503673241266/Test_openjdk8_hs_sanity.system_arm_linux_testList_2.tap'
[2025-06-19T21:48:57.669Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_sanity.system_arm_linux/builds/463/tap-master-files/Test_openjdk8_hs_sanity.system_arm_linux_testList_2/5/aqa-tests/TKG/output_17503673241266/Test_openjdk8_hs_sanity.system_arm_linux_testList_2.tap].
[2025-06-19T21:48:57.678Z] There are failed test cases. Marking build as UNSTABLE
[2025-06-19T21:48:57.678Z] TAP Reports Processing: FINISH
[Pipeline] echo
[2025-06-19T21:48:57.689Z] Saving Test_openjdk8_hs_sanity.system_arm_linux_testList_2/5/**/*.tap file on jenkins.
[Pipeline] archiveArtifacts
[2025-06-19T21:48:57.873Z] Archiving artifacts
[2025-06-19T21:48:58.227Z] Recording fingerprints
[Pipeline] echo
[2025-06-19T21:48:58.423Z] Test_openjdk8_hs_sanity.system_arm_linux_testList_1 #5 completed with status SUCCESS
[Pipeline] timeout
[2025-06-19T21:48:58.425Z] Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] copyArtifacts
[2025-06-19T21:48:59.507Z] Copied 1 artifact from "Test_openjdk8_hs_sanity.system_arm_linux_testList_1" build number 5
[Pipeline] }
[Pipeline] // timeout
[Pipeline] step
[2025-06-19T21:48:59.724Z] TAP Reports Processing: START
[2025-06-19T21:48:59.725Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_sanity.system_arm_linux_testList_1/5/**/*.tap
[2025-06-19T21:48:59.900Z] Saving reports...
[2025-06-19T21:49:00.077Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_sanity.system_arm_linux/builds/463/tap-master-files/Test_openjdk8_hs_sanity.system_arm_linux_testList_1/5/aqa-tests/TKG/output_17503678586798/Test_openjdk8_hs_sanity.system_arm_linux_testList_1.tap'
[2025-06-19T21:49:00.077Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_sanity.system_arm_linux/builds/463/tap-master-files/Test_openjdk8_hs_sanity.system_arm_linux_testList_1/5/aqa-tests/TKG/output_17503678586798/Test_openjdk8_hs_sanity.system_arm_linux_testList_1.tap].
[2025-06-19T21:49:00.100Z] TAP Reports Processing: FINISH
[Pipeline] echo
[2025-06-19T21:49:00.106Z] Saving Test_openjdk8_hs_sanity.system_arm_linux_testList_1/5/**/*.tap file on jenkins.
[Pipeline] archiveArtifacts
[2025-06-19T21:49:00.290Z] Archiving artifacts
[2025-06-19T21:49:00.641Z] Recording fingerprints
[Pipeline] echo
[2025-06-19T21:49:00.831Z] Test_openjdk8_hs_sanity.system_arm_linux_testList_0 #7 completed with status UNSTABLE
[Pipeline] timeout
[2025-06-19T21:49:00.833Z] Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] copyArtifacts
[2025-06-19T21:49:02.099Z] Copied 1 artifact from "Test_openjdk8_hs_sanity.system_arm_linux_testList_0" build number 7
[Pipeline] }
[Pipeline] // timeout
[Pipeline] step
[2025-06-19T21:49:02.331Z] TAP Reports Processing: START
[2025-06-19T21:49:02.331Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_sanity.system_arm_linux_testList_0/7/**/*.tap
[2025-06-19T21:49:02.506Z] Saving reports...
[2025-06-19T21:49:02.683Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_sanity.system_arm_linux/builds/463/tap-master-files/Test_openjdk8_hs_sanity.system_arm_linux_testList_0/7/aqa-tests/TKG/output_17503678081665/Test_openjdk8_hs_sanity.system_arm_linux_testList_0.tap'
[2025-06-19T21:49:02.683Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_sanity.system_arm_linux/builds/463/tap-master-files/Test_openjdk8_hs_sanity.system_arm_linux_testList_0/7/aqa-tests/TKG/output_17503678081665/Test_openjdk8_hs_sanity.system_arm_linux_testList_0.tap].
[2025-06-19T21:49:02.692Z] There are failed test cases. Marking build as UNSTABLE
[2025-06-19T21:49:02.706Z] TAP Reports Processing: FINISH
[Pipeline] echo
[2025-06-19T21:49:02.715Z] Saving Test_openjdk8_hs_sanity.system_arm_linux_testList_0/7/**/*.tap file on jenkins.
[Pipeline] archiveArtifacts
[2025-06-19T21:49:02.898Z] Archiving artifacts
[2025-06-19T21:49:03.254Z] Recording fingerprints
[Pipeline] findFiles
[Pipeline] readFile
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
[Pipeline] findFiles
[Pipeline] echo
[2025-06-19T21:49:06.345Z] Tap file found: Test_openjdk8_hs_sanity.system_arm_linux_testList_2/5/aqa-tests/TKG/output_17503673241266/Test_openjdk8_hs_sanity.system_arm_linux_testList_2.tap...
[Pipeline] readFile
[Pipeline] findFiles
[Pipeline] echo
[2025-06-19T21:49:07.253Z] Tap file found: Test_openjdk8_hs_sanity.system_arm_linux_testList_1/5/aqa-tests/TKG/output_17503678586798/Test_openjdk8_hs_sanity.system_arm_linux_testList_1.tap...
[Pipeline] readFile
[Pipeline] findFiles
[Pipeline] echo
[2025-06-19T21:49:08.144Z] Tap file found: Test_openjdk8_hs_sanity.system_arm_linux_testList_0/7/aqa-tests/TKG/output_17503678081665/Test_openjdk8_hs_sanity.system_arm_linux_testList_0.tap...
[Pipeline] readFile
[Pipeline] echo
[2025-06-19T21:49:08.420Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=TestJlmRemoteClassAuth_2,TestJlmRemoteThreadAuth_2&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=arm_linux&GENERATE_JOBS=true&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=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=8&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faarch32-jdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-linux-arm-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=&TEST_TIME=120&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=false&BUILD_LIST=system&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=484&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None
[Pipeline] cleanWs
[2025-06-19T21:49:08.829Z] [WS-CLEANUP] Deleting project workspace...
[2025-06-19T21:49:08.829Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration...
[2025-06-19T21:49:09.007Z] [WS-CLEANUP] done
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Rerun)
[Pipeline] echo
[2025-06-19T21:49:09.139Z] allocate a node for generating rerun job ...
[Pipeline] node
[2025-06-19T21:49:09.175Z] Running on test-docker-ubuntu2404-armv7-7 in /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux
[Pipeline] {
[Pipeline] echo
[2025-06-19T21:49:09.202Z] Generating rerun Test_openjdk8_hs_sanity.system_arm_linux_rerun job for running failed test(s) ...
[Pipeline] parallel
[Pipeline] { (Branch: Test_openjdk8_hs_sanity.system_arm_linux_rerun)
[Pipeline] echo
[2025-06-19T21:49:09.266Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_sanity.system_arm_linux_rerun params for generating the job
[Pipeline] fileExists
[Pipeline] sh
[2025-06-19T21:49:10.974Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate
[Pipeline] jobDsl
[2025-06-19T21:49:12.017Z] Processing DSL script testJobTemplate
[2025-06-19T21:52:38.969Z] LEVELS: [sanity]
[2025-06-19T21:52:38.969Z] JDK_VERSIONS: [8]
[2025-06-19T21:52:38.969Z] GROUPS: [system]
[2025-06-19T21:52:38.969Z] ARCH_OS_LIST: [arm_linux]
[2025-06-19T21:52:39.100Z] Added items:
[2025-06-19T21:52:39.100Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_rerun'}
[2025-06-19T21:52:39.100Z] Existing items:
[2025-06-19T21:52:39.100Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_0'}
[2025-06-19T21:52:39.100Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_1'}
[2025-06-19T21:52:39.100Z] GeneratedJob{name='Test_openjdk8_hs_sanity.system_arm_linux_testList_2'}
[Pipeline] }
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
[2025-06-19T21:52:40.067Z] Triggering rerun jobs in parallel ...
[Pipeline] parallel
[Pipeline] { (Branch: Test_openjdk8_hs_sanity.system_arm_linux_rerun)
[Pipeline] build
[2025-06-19T21:52:40.105Z] Scheduling project: Test_openjdk8_hs_sanity.system_arm_linux_rerun
[2025-06-19T21:52:45.361Z] Starting building: Test_openjdk8_hs_sanity.system_arm_linux_rerun #15
[2025-06-19T22:04:37.281Z] Build Test_openjdk8_hs_sanity.system_arm_linux_rerun #15 completed: UNSTABLE
[Pipeline] }
[Pipeline] // parallel
[Pipeline] node
[2025-06-19T22:04:37.408Z] Running on test-rise-ubuntu2404-riscv64-9 in /home/jenkins/workspace/Test_openjdk8_hs_sanity.system_arm_linux
[Pipeline] {
[Pipeline] cleanWs
[2025-06-19T22:04:37.482Z] [WS-CLEANUP] Deleting project workspace...
[2025-06-19T22:04:37.482Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration...
[2025-06-19T22:04:37.518Z] [WS-CLEANUP] done
[Pipeline] echo
[2025-06-19T22:04:37.531Z] Test_openjdk8_hs_sanity.system_arm_linux_rerun #15 completed with status UNSTABLE
[Pipeline] timeout
[2025-06-19T22:04:37.535Z] Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] copyArtifacts
[2025-06-19T22:04:37.766Z] Copied 1 artifact from "Test_openjdk8_hs_sanity.system_arm_linux_rerun" build number 15
[Pipeline] }
[Pipeline] // timeout
[Pipeline] step
[2025-06-19T22:04:37.843Z] TAP Reports Processing: START
[2025-06-19T22:04:37.843Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_sanity.system_arm_linux_rerun/15/**/*.tap
[2025-06-19T22:04:37.880Z] Saving reports...
[2025-06-19T22:04:37.971Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_sanity.system_arm_linux/builds/463/tap-master-files/Test_openjdk8_hs_sanity.system_arm_linux_rerun/15/aqa-tests/TKG/output_17503701286701/Test_openjdk8_hs_sanity.system_arm_linux_rerun.tap'
[2025-06-19T22:04:37.971Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_sanity.system_arm_linux/builds/463/tap-master-files/Test_openjdk8_hs_sanity.system_arm_linux_rerun/15/aqa-tests/TKG/output_17503701286701/Test_openjdk8_hs_sanity.system_arm_linux_rerun.tap].
[2025-06-19T22:04:37.977Z] There are failed test cases. Marking build as UNSTABLE
[2025-06-19T22:04:37.996Z] TAP Reports Processing: FINISH
[Pipeline] echo
[2025-06-19T22:04:38.004Z] Saving Test_openjdk8_hs_sanity.system_arm_linux_rerun/15/**/*.tap file on jenkins.
[Pipeline] archiveArtifacts
[2025-06-19T22:04:38.035Z] Archiving artifacts
[2025-06-19T22:04:38.126Z] Recording fingerprints
[Pipeline] findFiles
[Pipeline] readFile
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues.
[Pipeline] cleanWs
[2025-06-19T22:04:38.995Z] [WS-CLEANUP] Deleting project workspace...
[2025-06-19T22:04:38.996Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration...
[2025-06-19T22:04:39.037Z] [WS-CLEANUP] done
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] End of Pipeline
Finished: UNSTABLE