Test Results Summary Service

Test_openjdk8_hs_extended.openjdk_x86-64_windows

Started by upstream project "build-scripts/jobs/jdk8u/jdk8u-windows-x64-temurin" build number 564 originally caused by: Started by upstream project "build-scripts/openjdk8-pipeline" build number 3008 originally caused by: Started by upstream project "build-scripts/utils/betaTrigger_8ea" build number 266 originally caused by: Started by timer Checking out git ${ADOPTOPENJDK_REPO} into /home/jenkins/.jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows@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_extended.openjdk_x86-64_windows@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 2480cb6f040d1f208ba3fa3684beaa4f7dcbb069 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2480cb6f040d1f208ba3fa3684beaa4f7dcbb069 # timeout=10 Commit message: "Set current build result based on Perf metrics. (#6369)" > git rev-list --no-walk 20c189de9f97f55af5b130fa309872a7ce12bf25 # timeout=10 First time build. Skipping changelog. [Pipeline] Start of Pipeline [Pipeline] timestamps [Pipeline] { [Pipeline] echo [2025-06-26T21:20:54.413Z] SPEC: win_x86-64 [Pipeline] echo [2025-06-26T21:20:54.414Z] LABEL: ci.role.test&&hw.arch.x86&&sw.os.windows [Pipeline] stage [Pipeline] { (Queue) [Pipeline] nodesByLabel [2025-06-26T21:20:54.424Z] Found a total of 4 nodes with the 'ci.role.test&&hw.arch.x86&&sw.os.windows' 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-26T21:20:54.429Z] dynamicAgents: [] [Pipeline] node [2025-06-26T21:20:54.657Z] Running on test-azure-win2022-x64-1 in c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows [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-26T21:20:54.681Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] cleanWs [2025-06-26T21:20:54.736Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T21:20:54.737Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T21:20:54.755Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // timeout [Pipeline] checkout [2025-06-26T21:20:54.803Z] The recommended git tool is: git [2025-06-26T21:20:54.845Z] No credentials specified [2025-06-26T21:20:54.865Z] Cloning the remote Git repository [2025-06-26T21:20:54.892Z] Cloning repository https://github.com/adoptium/aqa-tests.git [2025-06-26T21:20:54.893Z] > git init c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests # timeout=10 [2025-06-26T21:20:55.011Z] [WARNING] Reference path does not exist: null/openjdk_cache [2025-06-26T21:20:55.011Z] Fetching upstream changes from https://github.com/adoptium/aqa-tests.git [2025-06-26T21:20:55.011Z] > git --version # timeout=10 [2025-06-26T21:20:55.068Z] > git --version # 'git version 2.39.0' [2025-06-26T21:20:55.068Z] > git fetch --tags --force --progress -- https://github.com/adoptium/aqa-tests.git +refs/heads/*:refs/remotes/origin/* # timeout=10 [2025-06-26T21:21:01.421Z] Avoid second fetch [2025-06-26T21:21:01.510Z] Checking out Revision 2480cb6f040d1f208ba3fa3684beaa4f7dcbb069 (origin/master) [2025-06-26T21:21:01.246Z] > git config remote.origin.url https://github.com/adoptium/aqa-tests.git # timeout=10 [2025-06-26T21:21:01.309Z] > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 [2025-06-26T21:21:01.430Z] > git rev-parse "origin/master^{commit}" # timeout=10 [2025-06-26T21:21:01.518Z] > git config core.sparsecheckout # timeout=10 [2025-06-26T21:21:01.588Z] > git checkout -f 2480cb6f040d1f208ba3fa3684beaa4f7dcbb069 # timeout=10 [2025-06-26T21:21:04.907Z] Commit message: "Set current build result based on Perf metrics. (#6369)" [Pipeline] } [Pipeline] // retry [Pipeline] load [Pipeline] { (c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows/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-26T21:21:16.156Z] Timeout set to expire in 1 day 1 hr [Pipeline] { [Pipeline] echo [2025-06-26T21:21:16.179Z] runMulticastCmd: false [Pipeline] stage [Pipeline] { (Setup) [Pipeline] sh [2025-06-26T21:21:16.681Z] + LC_TIME=C [2025-06-26T21:21:16.681Z] + date '+%a, %d %b %Y %T %z' [Pipeline] echo [2025-06-26T21:21:16.773Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-26T21:21:17.212Z] + aqa-tests/terminateTestProcesses.sh null [2025-06-26T21:21:17.212Z] Windows machine, using powershell queries... [2025-06-26T21:21:17.918Z] 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-26T21:21:19.153Z] + printenv [2025-06-26T21:21:19.153Z] ProgramFiles(x86)=C:\Program Files (x86) [2025-06-26T21:21:19.153Z] CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files [2025-06-26T21:21:19.153Z] !ExitCode=00000000 [2025-06-26T21:21:19.153Z] KEEP_WORKSPACE=false [2025-06-26T21:21:19.153Z] NUMBER_OF_PROCESSORS=4 [2025-06-26T21:21:19.153Z] PROCESSOR_LEVEL=6 [2025-06-26T21:21:19.153Z] TAP_NAME=Test_openjdk8_hs_extended.openjdk_x86-64_windows.tap [2025-06-26T21:21:19.153Z] LIB_DIR=c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib [2025-06-26T21:21:19.153Z] EXIT_FAILURE=false [2025-06-26T21:21:19.153Z] JDK_BRANCH=jdk8u462-b07_adopt [2025-06-26T21:21:19.153Z] RUN_TESTS_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_x86-64_windows/223/display/redirect?page=tests [2025-06-26T21:21:19.153Z] PLATFORM=x86-64_windows [2025-06-26T21:21:19.153Z] DOCKER_REQUIRED=false [2025-06-26T21:21:19.153Z] USERDOMAIN_ROAMINGPROFILE=TESTWIN2022DC [2025-06-26T21:21:19.153Z] PROGRAMFILES=C:\Program Files [2025-06-26T21:21:19.153Z] git=C:\Program Files\Git\cmd\git.exe [2025-06-26T21:21:19.153Z] TIME_LIMIT=25 [2025-06-26T21:21:19.153Z] JENKINS_SERVER_COOKIE=durable-2422130e19bafc74daf749e741d1935ac8733583bef6dd9354558da43e2c3bd0 [2025-06-26T21:21:19.153Z] PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC [2025-06-26T21:21:19.153Z] JAVA_HOME=C:\openjdk\jdk-8 [2025-06-26T21:21:19.153Z] OPENJ9_REPO=https://github.com/eclipse-openj9/openj9.git [2025-06-26T21:21:19.153Z] GENERATE_JOBS=true [2025-06-26T21:21:19.153Z] OPENJCEPLUS_GIT_REPO=https://github.com/ibmruntimes/OpenJCEPlus.git [2025-06-26T21:21:19.153Z] OS=Windows_NT [2025-06-26T21:21:19.153Z] RUN_CHANGES_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_x86-64_windows/223/display/redirect?page=changes [2025-06-26T21:21:19.153Z] HOMEDRIVE=C: [2025-06-26T21:21:19.153Z] ANT_HOME=C:\apache-ant\apache-ant-1.10.15 [2025-06-26T21:21:19.153Z] RERUN_ITERATIONS=1 [2025-06-26T21:21:19.153Z] OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse:master [2025-06-26T21:21:19.153Z] USERDOMAIN=TESTWIN2022DC [2025-06-26T21:21:19.153Z] STF_OWNER_BRANCH=adoptium:master [2025-06-26T21:21:19.153Z] HUDSON_HOME=/home/jenkins/.jenkins [2025-06-26T21:21:19.153Z] PWD=/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows [2025-06-26T21:21:19.153Z] USERPROFILE=C:\Users\jenkins [2025-06-26T21:21:19.153Z] ARCHIVE_TEST_RESULTS=false [2025-06-26T21:21:19.153Z] SETUP_JCK_RUN=false [2025-06-26T21:21:19.153Z] BUILD_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_x86-64_windows/223/ [2025-06-26T21:21:19.153Z] SLACK_CHANNEL=aqavit-bot [2025-06-26T21:21:19.153Z] UPSTREAM_JOB_NAME=build-scripts/jobs/jdk8u/jdk8u-windows-x64-temurin [2025-06-26T21:21:19.153Z] JCK_GIT_BRANCH=master [2025-06-26T21:21:19.153Z] JOB_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_x86-64_windows/ [2025-06-26T21:21:19.153Z] BUILD_NUMBER=223 [2025-06-26T21:21:19.153Z] TKG_ITERATIONS=1 [2025-06-26T21:21:19.153Z] _=/usr/bin/printenv [2025-06-26T21:21:19.153Z] VS140COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\ [2025-06-26T21:21:19.153Z] PERF_ROOT=c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../benchmarks [2025-06-26T21:21:19.153Z] ALLUSERSPROFILE=C:\ProgramData [2025-06-26T21:21:19.153Z] JENKINS_NODE_COOKIE=fbc5f406-5185-49c0-ba28-b3283f317363 [2025-06-26T21:21:19.153Z] CommonProgramW6432=C:\Program Files\Common Files [2025-06-26T21:21:19.153Z] KEEP_REPORTDIR=true [2025-06-26T21:21:19.153Z] BUILD_DISPLAY_NAME=#223 [2025-06-26T21:21:19.153Z] SDK_RESOURCE=upstream [2025-06-26T21:21:19.153Z] TEST_JDK_HOME=c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows/jdkbinary/j2sdk-image [2025-06-26T21:21:19.153Z] HOME=/home/jenkins [2025-06-26T21:21:19.153Z] USERNAME=jenkins [2025-06-26T21:21:19.153Z] COMSPEC=C:\Windows\system32\cmd.exe [2025-06-26T21:21:19.153Z] CUDA_PATH_V9_1=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1 [2025-06-26T21:21:19.153Z] JENKINS_URL=https://ci.adoptium.net/ [2025-06-26T21:21:19.153Z] JOB_BASE_NAME=Test_openjdk8_hs_extended.openjdk_x86-64_windows [2025-06-26T21:21:19.153Z] JOBSTARTTIME=Thu, 26 Jun 2025 21:21:16 +0000 [2025-06-26T21:21:19.153Z] JDK_VERSION=8 [2025-06-26T21:21:19.153Z] APPDATA=C:\Users\jenkins\AppData\Roaming [2025-06-26T21:21:19.153Z] JOB_NAME=Test_openjdk8_hs_extended.openjdk_x86-64_windows [2025-06-26T21:21:19.153Z] USE_TESTENV_PROPERTIES=false [2025-06-26T21:21:19.153Z] SYSTEMROOT=C:\Windows [2025-06-26T21:21:19.153Z] PERSONAL_BUILD=false [2025-06-26T21:21:19.153Z] RUN_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_x86-64_windows/223/display/redirect [2025-06-26T21:21:19.153Z] LOCALAPPDATA=C:\Users\jenkins\AppData\Local [2025-06-26T21:21:19.153Z] AUTO_DETECT=true [2025-06-26T21:21:19.153Z] EXIT_SUCCESS=false [2025-06-26T21:21:19.153Z] JOB_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_x86-64_windows/display/redirect [2025-06-26T21:21:19.153Z] PROMPT=$P$G [2025-06-26T21:21:19.153Z] WORKSPACE=c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows [2025-06-26T21:21:19.153Z] COMPUTERNAME=TESTWIN2022DC [2025-06-26T21:21:19.153Z] OPENJ9_BRANCH=master [2025-06-26T21:21:19.153Z] EXTERNAL_CUSTOM_BRANCH=master [2025-06-26T21:21:19.153Z] SYSTEM_LIB_DIR=c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/system_lib [2025-06-26T21:21:19.153Z] PARALLEL=Dynamic [2025-06-26T21:21:19.153Z] HUDSON_URL=https://ci.adoptium.net/ [2025-06-26T21:21:19.153Z] ITERATIONS=1 [2025-06-26T21:21:19.153Z] UPSTREAM_JOB_NUMBER=564 [2025-06-26T21:21:19.153Z] SPEC=win_x86-64 [2025-06-26T21:21:19.153Z] TERM=xterm-256color [2025-06-26T21:21:19.153Z] JDK_REPO=https://github.com/adoptium/jdk8u [2025-06-26T21:21:19.153Z] ADOPTOPENJDK_SYSTEMTEST_OWNER_BRANCH=adoptium:master [2025-06-26T21:21:19.153Z] LOGONSERVER=\\TESTWIN2022DC [2025-06-26T21:21:19.153Z] NODE_NAME=test-azure-win2022-x64-1 [2025-06-26T21:21:19.153Z] ADOPTOPENJDK_REPO=https://github.com/adoptium/aqa-tests.git [2025-06-26T21:21:19.153Z] PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\Windows\system32\WindowsPowerShell\v1.0\Modules [2025-06-26T21:21:19.153Z] HUDSON_SERVER_COOKIE=2d832652af5afba8 [2025-06-26T21:21:19.153Z] CUDA_PATH=C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.1 [2025-06-26T21:21:19.153Z] WIX=C:\Program Files (x86)\WiX Toolset v3.14\ [2025-06-26T21:21:19.153Z] TEMP=/cygdrive/c/Users/jenkins/AppData/Local/Temp/2 [2025-06-26T21:21:19.153Z] DYNAMIC_COMPILE=false [2025-06-26T21:21:19.153Z] SHLVL=2 [2025-06-26T21:21:19.153Z] BUILD_TAG=jenkins-Test_openjdk8_hs_extended.openjdk_x86-64_windows-223 [2025-06-26T21:21:19.153Z] PROCESSOR_REVISION=5504 [2025-06-26T21:21:19.153Z] DriverData=C:\Windows\System32\Drivers\DriverData [2025-06-26T21:21:19.153Z] EXECUTOR_NUMBER=0 [2025-06-26T21:21:19.153Z] HUDSON_COOKIE=915668e2-0400-45bf-b010-5c5df46cacb6 [2025-06-26T21:21:19.153Z] ADOPTOPENJDK_BRANCH=master [2025-06-26T21:21:19.153Z] JENKINS_HOME=/home/jenkins/.jenkins [2025-06-26T21:21:19.153Z] COMMONPROGRAMFILES=C:\Program Files\Common Files [2025-06-26T21:21:19.153Z] ORIGIN_JDK_VERSION=8 [2025-06-26T21:21:19.153Z] PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 85 Stepping 4, GenuineIntel [2025-06-26T21:21:19.153Z] SESSIONNAME=RDP-Tcp#40 [2025-06-26T21:21:19.153Z] NUM_PROCESSORS=2 [2025-06-26T21:21:19.153Z] CUSTOMIZED_SDK_URL_CREDENTIAL_ID=eclipse_temurin_bot_email_and_token [2025-06-26T21:21:19.153Z] NODE_LABELS=sw.os.windows test ci.role.test test-azure-win2022-x64-1 x64 windows hw.arch.x86 win2022 [2025-06-26T21:21:19.153Z] STAGE_NAME=Setup [2025-06-26T21:21:19.153Z] EXTERNAL_TEST_CMD=mvn clean install [2025-06-26T21:21:19.153Z] TEST_TIME=120 [2025-06-26T21:21:19.153Z] HOMEPATH=\Users\jenkins [2025-06-26T21:21:19.153Z] WORKSPACE_TMP=c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows@tmp [2025-06-26T21:21:19.153Z] TMP=/cygdrive/c/Users/jenkins/AppData/Local/Temp/2 [2025-06-26T21:21:19.153Z] PATH=/usr/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Windows/System32/OpenSSH:/cygdrive/c/Program Files/dotnet:/cygdrive/c/Users/adoptopenjdk/AppData/Local/Microsoft/WindowsApps:/cygdrive/c/Strawberry/perl/bin:/cygdrive/c/Program Files/Git/cmd:/cygdrive/c/openjdk/jdk-8/bin:/cygdrive/c/apache-ant/apache-ant-1.10.15/bin:/cygdrive/c/Program Files (x86)/IncrediBuild:/cygdrive/c/Program Files (x86)/Windows Kits/10/Windows Performance Toolkit:/cygdrive/c/rust/bin:/cygdrive/c/Program Files/IcedTeaWEB/bin:/cygdrive/c/Program Files/Microsoft SQL Server/110/Tools/Binn:/cygdrive/c/Program Files (x86)/Microsoft SDKs/TypeScript/1.0:/cygdrive/c/Program Files/Microsoft SQL Server/120/Tools/Binn:/cygdrive/c/Users/jenkins/AppData/Local/Microsoft/WindowsApps [2025-06-26T21:21:19.153Z] LIGHT_WEIGHT_CHECKOUT=false [2025-06-26T21:21:19.153Z] TKG_OWNER_BRANCH=adoptium:master [2025-06-26T21:21:19.153Z] ProgramW6432=C:\Program Files [2025-06-26T21:21:19.153Z] CI=true [2025-06-26T21:21:19.153Z] RUN_ARTIFACTS_DISPLAY_URL=https://ci.adoptium.net/job/Test_openjdk8_hs_extended.openjdk_x86-64_windows/223/display/redirect?page=artifacts [2025-06-26T21:21:19.153Z] ACTIVE_NODE_TIMEOUT=5 [2025-06-26T21:21:19.153Z] RERUN_FAILURE=true [2025-06-26T21:21:19.153Z] VS120COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\ [2025-06-26T21:21:19.153Z] VS110COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\ [2025-06-26T21:21:19.153Z] OPENJCEPLUS_GIT_BRANCH=semeru-java8 [2025-06-26T21:21:19.153Z] BUILD_LIST=openjdk [2025-06-26T21:21:19.153Z] BUILD_ID=223 [2025-06-26T21:21:19.153Z] WINDIR=C:\Windows [2025-06-26T21:21:19.153Z] PROCESSOR_ARCHITECTURE=AMD64 [2025-06-26T21:21:19.153Z] PUBLIC=C:\Users\Public [2025-06-26T21:21:19.153Z] CLIENTNAME=scfryer-thinkpa [2025-06-26T21:21:19.153Z] SYSTEMDRIVE=C: [2025-06-26T21:21:19.153Z] TARGET=extended.openjdk [2025-06-26T21:21:19.153Z] USE_JRE=false [2025-06-26T21:21:19.153Z] JDK_IMPL=hotspot [2025-06-26T21:21:19.153Z] ProgramData=C:\ProgramData 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-26T21:21:19.212Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] dir [2025-06-26T21:21:19.234Z] Running in c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\jdkbinary [Pipeline] { [Pipeline] copyArtifacts [2025-06-26T21:21:25.257Z] Copied 5 artifacts from "build-scripts » jobs » jdk8u » jdk8u-windows-x64-temurin" build number 564 [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-26T21:21:25.462Z] 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-26T21:21:25.468Z] Running in c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows [Pipeline] { [Pipeline] sshagent [2025-06-26T21:21:25.491Z] $ ssh-agent [2025-06-26T21:21:25.633Z] SSH_AUTH_SOCK=/tmp/ssh-SHauYNCn4tt8/agent.472 [2025-06-26T21:21:25.633Z] SSH_AGENT_PID=473 [2025-06-26T21:21:25.633Z] [ssh-agent] Started. [Pipeline] { [Pipeline] dir [2025-06-26T21:21:25.649Z] Running in c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests [Pipeline] { [Pipeline] withCredentials [2025-06-26T21:21:25.691Z] Masking supported pattern matches of %USERNAME% or %PASSWORD% [Pipeline] { [Pipeline] sh [2025-06-26T21:21:26.221Z] ++ pwd [2025-06-26T21:21:26.221Z] + ./get.sh -s /cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/.. -p x86-64_windows -r upstream -j 8 -i hotspot --clone_openj9 false --tkg_repo https://github.com/adoptium/TKG.git --tkg_branch master [2025-06-26T21:21:26.571Z] TESTDIR: /cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests [2025-06-26T21:21:26.571Z] get jdk binary... [2025-06-26T21:21:26.571Z] --sdkdir is set to upstream. Therefore, skip download jdk binary [2025-06-26T21:21:26.571Z] Uncompressing file: OpenJDK8U-jdk_x64_windows_hotspot_8u462b07-ea.zip ... [2025-06-26T21:21:29.535Z] List files in jdkbinary folder... [2025-06-26T21:21:29.535Z] total 173956 [2025-06-26T21:21:29.535Z] -rwxrwx---+ 1 jenkins None 30390534 Jun 26 20:44 OpenJDK8U-debugimage_x64_windows_hotspot_8u462b07-ea.zip [2025-06-26T21:21:29.535Z] -rwxrwx---+ 1 jenkins None 106974444 Jun 26 20:54 OpenJDK8U-jdk_x64_windows_hotspot_8u462b07-ea.zip [2025-06-26T21:21:29.535Z] -rwxrwx---+ 1 jenkins None 40654204 Jun 26 20:55 OpenJDK8U-jre_x64_windows_hotspot_8u462b07-ea.zip [2025-06-26T21:21:29.535Z] -rwxrwx---+ 1 jenkins None 24015 Jun 26 20:49 OpenJDK8U-sbom_x64_windows_hotspot_8u462b07-ea-metadata.json [2025-06-26T21:21:29.535Z] -rwxrwx---+ 1 jenkins None 79159 Jun 26 21:11 OpenJDK8U-sbom_x64_windows_hotspot_8u462b07-ea.json [2025-06-26T21:21:29.535Z] drwxrwxr-x+ 1 jenkins None 0 Jun 26 21:21 tmp [2025-06-26T21:21:29.535Z] List files in jdkbinary/tmp folder... [2025-06-26T21:21:29.535Z] total 4 [2025-06-26T21:21:29.535Z] drwxrwxr-x+ 1 jenkins None 0 Jun 26 20:44 jdk8u462-b07 [2025-06-26T21:21:29.535Z] Moving directory jdk8u462-b07/ to ../j2sdk-image [2025-06-26T21:21:29.535Z] Uncompressing file: OpenJDK8U-jre_x64_windows_hotspot_8u462b07-ea.zip ... [2025-06-26T21:21:30.687Z] List files in jdkbinary folder... [2025-06-26T21:21:30.687Z] total 173960 [2025-06-26T21:21:30.687Z] -rwxrwx---+ 1 jenkins None 30390534 Jun 26 20:44 OpenJDK8U-debugimage_x64_windows_hotspot_8u462b07-ea.zip [2025-06-26T21:21:30.687Z] -rwxrwx---+ 1 jenkins None 106974444 Jun 26 20:54 OpenJDK8U-jdk_x64_windows_hotspot_8u462b07-ea.zip [2025-06-26T21:21:30.687Z] -rwxrwx---+ 1 jenkins None 40654204 Jun 26 20:55 OpenJDK8U-jre_x64_windows_hotspot_8u462b07-ea.zip [2025-06-26T21:21:30.687Z] -rwxrwx---+ 1 jenkins None 24015 Jun 26 20:49 OpenJDK8U-sbom_x64_windows_hotspot_8u462b07-ea-metadata.json [2025-06-26T21:21:30.687Z] -rwxrwx---+ 1 jenkins None 79159 Jun 26 21:11 OpenJDK8U-sbom_x64_windows_hotspot_8u462b07-ea.json [2025-06-26T21:21:30.687Z] drwxrwxr-x+ 1 jenkins None 0 Jun 26 20:44 j2sdk-image [2025-06-26T21:21:30.687Z] drwxrwxr-x+ 1 jenkins None 0 Jun 26 21:21 tmp [2025-06-26T21:21:30.687Z] List files in jdkbinary/tmp folder... [2025-06-26T21:21:30.687Z] total 4 [2025-06-26T21:21:30.687Z] drwxrwxr-x+ 1 jenkins None 0 Jun 26 20:44 jdk8u462-b07-jre [2025-06-26T21:21:30.687Z] Moving directory jdk8u462-b07-jre/ to ../j2re-image [2025-06-26T21:21:30.687Z] Uncompressing OpenJDK8U-debugimage_x64_windows_hotspot_8u462b07-ea.zip over ./j2sdk-image/jre... [2025-06-26T21:21:32.347Z] Removing top-level folder jdk8u462-b07-debug-image/ [2025-06-26T21:21:32.347Z] Removing top-level folder jdk8u462-b07/ [2025-06-26T21:21:34.620Z] Run c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows/jdkbinary/j2sdk-image/bin/java -version [2025-06-26T21:21:34.620Z] =JAVA VERSION OUTPUT BEGIN= [2025-06-26T21:21:34.620Z] openjdk version "1.8.0_462-beta" [2025-06-26T21:21:34.620Z] OpenJDK Runtime Environment (Temurin)(build 1.8.0_462-beta-202506262009-b07) [2025-06-26T21:21:34.620Z] OpenJDK 64-Bit Server VM (Temurin)(build 25.462-b07, mixed mode) [2025-06-26T21:21:34.620Z] =JAVA VERSION OUTPUT END= [2025-06-26T21:21:34.620Z] =RELEASE INFO BEGIN= [2025-06-26T21:21:34.620Z] JAVA_VERSION="1.8.0_462" [2025-06-26T21:21:34.620Z] OS_NAME="Windows" [2025-06-26T21:21:34.620Z] OS_VERSION="5.2" [2025-06-26T21:21:34.620Z] OS_ARCH="amd64" [2025-06-26T21:21:34.620Z] SOURCE=".:git:d1f0ddc52725+" [2025-06-26T21:21:34.620Z] IMPLEMENTOR="Eclipse Adoptium" [2025-06-26T21:21:34.620Z] BUILD_SOURCE="git:5ec7cf95adce133a225cf1832d4b4915130b6a2a" [2025-06-26T21:21:34.620Z] BUILD_SOURCE_REPO="https://github.com/adoptium/temurin-build.git" [2025-06-26T21:21:34.620Z] SOURCE_REPO="https://github.com/adoptium/jdk8u.git" [2025-06-26T21:21:34.620Z] FULL_VERSION="1.8.0_462-beta-202506262009-b07" [2025-06-26T21:21:34.620Z] SEMANTIC_VERSION="8.0.462+7" [2025-06-26T21:21:34.620Z] BUILD_INFO="OS: Windows Server 2022 Version: 10.0" [2025-06-26T21:21:34.620Z] JVM_VARIANT="Hotspot" [2025-06-26T21:21:34.620Z] JVM_VERSION="25.462-b07" [2025-06-26T21:21:34.620Z] IMAGE_TYPE="JDK" [2025-06-26T21:21:34.620Z] =RELEASE INFO END= [2025-06-26T21:21:34.620Z] get testKitGen... [2025-06-26T21:21:34.620Z] git clone -q https://github.com/adoptium/TKG.git [2025-06-26T21:21:36.335Z] git rev-parse master [2025-06-26T21:21:36.335Z] git checkout -q -f 1828e310fd8fb3115fde605c41aea434b90143d0 [Pipeline] } [Pipeline] // withCredentials [Pipeline] } [Pipeline] // dir [Pipeline] } [2025-06-26T21:21:36.784Z] $ ssh-agent -k [2025-06-26T21:21:36.839Z] unset SSH_AUTH_SOCK; [2025-06-26T21:21:36.839Z] unset SSH_AGENT_PID; [2025-06-26T21:21:36.839Z] echo Agent pid 473 killed; [2025-06-26T21:21:36.895Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] fileExists [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T21:21:37.292Z] Rerun in Grinder: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=extended.openjdk&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=5&VENDOR_TEST_DIRS=&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=x86-64_windows&GENERATE_JOBS=true&KEEP_REPORTDIR=true&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=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%2Fjdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-windows-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk8u462-b07_adopt&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=openjdk&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=564&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] echo [2025-06-26T21:21:37.318Z] Rerun in Grinder on same machine: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=extended.openjdk&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=5&VENDOR_TEST_DIRS=&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=x86-64_windows&GENERATE_JOBS=true&KEEP_REPORTDIR=true&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=test-azure-win2022-x64-1&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%2Fjdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-windows-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk8u462-b07_adopt&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=openjdk&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=564&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-26T21:21:37.358Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-26T21:21:37.499Z] Copied 1 artifact from "getTRSSOutput" build number 1816 [Pipeline] sh [2025-06-26T21:21:37.976Z] + cd ./aqa-tests/TKG/resources/TRSS [2025-06-26T21:21:37.976Z] + gzip -cd TRSSOutput.tar.gz [2025-06-26T21:21:37.976Z] + tar xof - [2025-06-26T21:21:38.310Z] + rm TRSSOutput.tar.gz [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-26T21:21:38.395Z] Timeout set to expire in 20 min [Pipeline] { [Pipeline] echo [2025-06-26T21:21:38.411Z] Custom URL: https://ci.adoptium.net//job/test.getDependency/lastSuccessfulBuild/artifact/ [Pipeline] sh [2025-06-26T21:21:38.892Z] + perl ./aqa-tests/TKG/scripts/getDependencies.pl -path c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib -task default -customUrl https://ci.adoptium.net//job/test.getDependency/lastSuccessfulBuild/artifact/ [2025-06-26T21:21:39.236Z] -------------------------------------------- [2025-06-26T21:21:39.236Z] path is set to c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib [2025-06-26T21:21:39.236Z] task is set to default [2025-06-26T21:21:39.236Z] dependencyList is set to all [2025-06-26T21:21:39.236Z] -------------------------------------------- [2025-06-26T21:21:39.236Z] Starting download third party dependent jars [2025-06-26T21:21:39.236Z] -------------------------------------------- [2025-06-26T21:21:39.236Z] downloading dependent third party jars to c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib [2025-06-26T21:21:39.236Z] c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib/jcommander.jar exists with correct hash, not downloading [2025-06-26T21:21:39.236Z] downloading https://ci.adoptium.net//job/test.getDependency/lastSuccessfulBuild/artifact//jtreg_7_5_2_1.tar.gz [2025-06-26T21:21:39.236Z] --> file downloaded to c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib/jtreg_7_5_2_1.tar.gz [2025-06-26T21:21:39.236Z] downloading https://ci.adoptium.net//job/test.getDependency/lastSuccessfulBuild/artifact//jtreg_7_5_2_1.tar.gz.sha256sum.txt [2025-06-26T21:21:39.576Z] ERROR: sha checksum error. [2025-06-26T21:21:39.576Z] --> file downloaded to c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib/jtreg_7_5_2_1.tar.gz.sha256sum.txt [2025-06-26T21:21:39.576Z] Expected sha is: [2025-06-26T21:21:39.576Z] , [2025-06-26T21:21:39.576Z] Actual sha is : 4cb9879fa512043ff67a05eec070883b673c9cad6c4af061f9d22090c59c9dd0. [2025-06-26T21:21:39.634Z] Please delete c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib/jtreg_7_5_2_1.tar.gz and rerun the program! [Pipeline] } [Pipeline] // timeout [Pipeline] echo [2025-06-26T21:21:39.685Z] Exception: hudson.AbortException: script returned exit code 255 [Pipeline] echo [2025-06-26T21:21:39.691Z] Cannot pre-stage test libs from c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/../../testDependency/lib on the machine. Skipping... [Pipeline] nodesByLabel [2025-06-26T21:21:39.711Z] Found a total of 4 nodes with the 'ci.role.test&&hw.arch.x86&&sw.os.windows' label [Pipeline] sh [2025-06-26T21:21:40.202Z] + cd ./aqa-tests/TKG [2025-06-26T21:21:40.202Z] ++ uname [2025-06-26T21:21:40.202Z] + '[' CYGWIN_NT-10.0-20348 = AIX ']' [2025-06-26T21:21:40.202Z] ++ uname [2025-06-26T21:21:40.202Z] + '[' CYGWIN_NT-10.0-20348 = SunOS ']' [2025-06-26T21:21:40.202Z] ++ uname [2025-06-26T21:21:40.202Z] + '[' CYGWIN_NT-10.0-20348 = '*BSD' ']' [2025-06-26T21:21:40.202Z] + MAKE=make [2025-06-26T21:21:40.202Z] + make genParallelList TEST=extended.openjdk TEST_TIME=120 NUM_MACHINES= [2025-06-26T21:21:40.202Z] JAVA_HOME is set to c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/jdkbinary/j2sdk-image [2025-06-26T21:21:40.528Z] LIB_DIR is set to C:/jenkins/testDependency/lib [2025-06-26T21:21:40.528Z] rm -f -r /cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG/../TKG/output_compilation; \ [2025-06-26T21:21:40.528Z] mkdir -p /cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG/../TKG/output_compilation; \ [2025-06-26T21:21:40.528Z] (ant -f ./scripts/build_tools.xml "-DTEST_JDK_HOME=c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/jdkbinary/j2sdk-image" "-DTEST_ROOT=/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG/.." "-DLIB_DIR=C:/jenkins/testDependency/lib" 2>&1; echo $? ) | tee "/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG/../TKG/output_compilation/compilation.log"; \ [2025-06-26T21:21:40.528Z] if [ -z "$(tail -1 /cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG/../TKG/output_compilation/compilation.log | grep 0)" ]; then perl scripts/moveDmp.pl --compileLogPath="/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG/../TKG/output_compilation/compilation.log" --testRoot="/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG/.."; false; else rm -f -r "/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG/../TKG/output_compilation"; fi [2025-06-26T21:21:41.687Z] Buildfile: C:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests\TKG\scripts\build_tools.xml [2025-06-26T21:21:42.029Z] [2025-06-26T21:21:42.029Z] build: [2025-06-26T21:21:42.029Z] [2025-06-26T21:21:42.029Z] clean: [2025-06-26T21:21:42.376Z] [2025-06-26T21:21:42.376Z] init: [2025-06-26T21:21:42.376Z] [mkdir] Created dir: C:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests\TKG\bin [2025-06-26T21:21:42.376Z] [2025-06-26T21:21:42.376Z] getDependentLibs: [2025-06-26T21:21:42.376Z] [exec] -------------------------------------------- [2025-06-26T21:21:42.376Z] [exec] path is set to C:/jenkins/testDependency/lib [2025-06-26T21:21:42.376Z] [exec] task is set to default [2025-06-26T21:21:42.376Z] [exec] dependencyList is set to json_simple [2025-06-26T21:21:42.376Z] [exec] -------------------------------------------- [2025-06-26T21:21:42.376Z] [exec] Starting download third party dependent jars [2025-06-26T21:21:42.376Z] [exec] -------------------------------------------- [2025-06-26T21:21:42.376Z] [exec] downloading dependent third party jars to C:/jenkins/testDependency/lib [2025-06-26T21:21:42.376Z] [exec] C:/jenkins/testDependency/lib/json-simple.jar exists with correct hash, not downloading [2025-06-26T21:21:42.376Z] [exec] downloaded dependent third party jars successfully [2025-06-26T21:21:42.376Z] [2025-06-26T21:21:42.376Z] compile: [2025-06-26T21:21:42.376Z] [echo] Ant version is Apache Ant(TM) version 1.10.15 compiled on August 25 2024 [2025-06-26T21:21:42.376Z] [echo] ============COMPILER SETTINGS============ [2025-06-26T21:21:42.376Z] [echo] ===fork: yes [2025-06-26T21:21:42.376Z] [echo] ===debug: on [2025-06-26T21:21:42.376Z] [javac] Compiling 28 source files to C:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests\TKG\bin [2025-06-26T21:21:45.380Z] [2025-06-26T21:21:45.380Z] dist: [2025-06-26T21:21:45.380Z] [jar] Building jar: C:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests\TKG\bin\TestKitGen.jar [2025-06-26T21:21:45.380Z] [2025-06-26T21:21:45.380Z] BUILD SUCCESSFUL [2025-06-26T21:21:45.380Z] Total time: 3 seconds [2025-06-26T21:21:45.380Z] 0 [2025-06-26T21:21:45.380Z] c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/jdkbinary/j2sdk-image/bin/java -cp ./bin/TestKitGen.jar org.openj9.envInfo.EnvDetector [2025-06-26T21:21:46.096Z] Unfamiliar microArch detected in TKG. It will not be added in TKG microArch! [2025-06-26T21:21:46.096Z] microArchOutput: model name : Intel(R) Xeon(R) Platinum 8168 CPU @ 2.70GHz [2025-06-26T21:21:47.761Z] ****************************** MACHINE INFO ****************************** [2025-06-26T21:21:47.761Z] File path : C:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests\TKG [2025-06-26T21:21:47.761Z] Free Physical Memory Size : 5639950336 [2025-06-26T21:21:47.761Z] Free space (bytes) : 135669891072 [2025-06-26T21:21:47.761Z] Total Physical Memory Size : 8536289280 [2025-06-26T21:21:47.761Z] Total space (bytes) : 274283311104 [2025-06-26T21:21:47.761Z] Usable space (bytes) : 135669891072 [2025-06-26T21:21:47.761Z] antVersion : Apache Ant(TM) version 1.10.15 compiled on August 25 2024 [2025-06-26T21:21:47.761Z] bashVersion : [2025-06-26T21:21:47.761Z] GNU bash, version 5.2.15(3)-release (x86_64-pc-cygwin) [2025-06-26T21:21:47.761Z] Copyright (C) 2022 Free Software Foundation, Inc. [2025-06-26T21:21:47.761Z] License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] This is free software; you are free to change and redistribute it. [2025-06-26T21:21:47.761Z] There is NO WARRANTY, to the extent permitted by law. [2025-06-26T21:21:47.761Z] cpuCores : 4 [2025-06-26T21:21:47.761Z] curlVersion : [2025-06-26T21:21:47.761Z] curl 8.3.0 (x86_64-pc-cygwin) libcurl/8.3.0 OpenSSL/1.1.1w zlib/1.3 brotli/1.0.9 zstd/1.5.5 libidn2/2.3.4 libpsl/0.21.2 (+libidn2/2.3.4) libssh2/1.11.0 nghttp2/1.56.0 libgsasl/2.2.0 OpenLDAP/2.6.6 [2025-06-26T21:21:47.761Z] Release-Date: 2023-09-13 [2025-06-26T21:21:47.761Z] Protocols: dict file ftp ftps gopher gophers http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp [2025-06-26T21:21:47.761Z] Features: alt-svc AsynchDNS brotli gsasl GSS-API HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile libz NTLM NTLM_WB PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd [2025-06-26T21:21:47.761Z] dockerVersion : bash: line 1: docker: command not found [2025-06-26T21:21:47.761Z] gcc version : 11 [2025-06-26T21:21:47.761Z] gclibc version : ldd (cygwin) 3.4.9 [2025-06-26T21:21:47.761Z] gdb version : bash: line 1: gdb: command not found [2025-06-26T21:21:47.761Z] lldb version : Command could not be executed [2025-06-26T21:21:47.761Z] makeVersion : [2025-06-26T21:21:47.761Z] GNU Make 4.4.1 [2025-06-26T21:21:47.761Z] Built for x86_64-pc-cygwin [2025-06-26T21:21:47.761Z] Copyright (C) 1988-2023 Free Software Foundation, Inc. [2025-06-26T21:21:47.761Z] License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html> [2025-06-26T21:21:47.761Z] This is free software: you are free to change and redistribute it. [2025-06-26T21:21:47.761Z] There is NO WARRANTY, to the extent permitted by law. [2025-06-26T21:21:47.761Z] mavenVersion : bash: line 1: mvn: command not found [2025-06-26T21:21:47.761Z] perlVersion : [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] This is perl 5, version 36, subversion 1 (v5.36.1) built for x86_64-cygwin-threads-multi [2025-06-26T21:21:47.761Z] (with 6 registered patches, see perl -V for more detail) [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] Copyright 1987-2023, Larry Wall [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] Perl may be copied only under the terms of either the Artistic License or the [2025-06-26T21:21:47.761Z] GNU General Public License, which may be found in the Perl 5 source kit. [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] Complete documentation for Perl, including FAQ lists, should be found on [2025-06-26T21:21:47.761Z] this system using "man perl" or "perldoc perl". If you have access to the [2025-06-26T21:21:47.761Z] Internet, point your browser at https://www.perl.org/, the Perl Home Page. [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] podmanVersion : bash: line 1: podman: command not found [2025-06-26T21:21:47.761Z] procArch : unknown [2025-06-26T21:21:47.761Z] sysArch : x86_64 [2025-06-26T21:21:47.761Z] sysOS : CYGWIN_NT-10.0-20348 [2025-06-26T21:21:47.761Z] ulimit : [2025-06-26T21:21:47.761Z] core file size (blocks, -c) unlimited [2025-06-26T21:21:47.761Z] data seg size (kbytes, -d) unlimited [2025-06-26T21:21:47.761Z] file size (blocks, -f) unlimited [2025-06-26T21:21:47.761Z] open files (-n) 3200 [2025-06-26T21:21:47.761Z] pipe size (512 bytes, -p) 8 [2025-06-26T21:21:47.761Z] stack size (kbytes, -s) 2032 [2025-06-26T21:21:47.761Z] cpu time (seconds, -t) unlimited [2025-06-26T21:21:47.761Z] max user processes (-u) 256 [2025-06-26T21:21:47.761Z] virtual memory (kbytes, -v) unlimited [2025-06-26T21:21:47.761Z] uname : CYGWIN_NT-10.0-20348 testwin2022dc 3.4.9-1.x86_64 2023-09-06 11:19 UTC x86_64 Cygwin [2025-06-26T21:21:47.761Z] vmVendor : Oracle Corporation [2025-06-26T21:21:47.761Z] vmVersion : 25.462-b07 [2025-06-26T21:21:47.761Z] xlc version : bash: line 1: xlC: command not found [2025-06-26T21:21:47.761Z] ************************************************************************** [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] System.getProperty('java.vm.name')=OpenJDK 64-Bit Server VM [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] System.getProperty('java.vendor')=Temurin [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] System.getProperty('os.name')=Windows Server 2022 [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] System.getProperty('os.arch')=amd64 [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] System.getProperty('java.fullversion')=null [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] System.getProperty('sun.arch.data.model')=64 [2025-06-26T21:21:47.761Z] [2025-06-26T21:21:47.761Z] make -f makeGen.mk AUTO_DETECT=true MODE=parallelList NUM_MACHINES= TEST_TIME=120 TESTTARGET=extended.openjdk TESTLIST= TRSS_URL= LIB_DIR=C:/jenkins/testDependency/lib [2025-06-26T21:21:48.085Z] make[1]: Entering directory '/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG' [2025-06-26T21:21:48.085Z] perl scripts/configure.pl [2025-06-26T21:21:48.085Z] c:/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/jdkbinary/j2sdk-image/bin/java -cp "./bin/TestKitGen.jar;C:/jenkins/testDependency/lib/json-simple.jar" org.testKitGen.MainRunner --mode=parallelList --spec=win_x86-64 --microArch="" --osLabel="" --jdkVersion=8 --impl=hotspot --vendor="temurin" --buildList=openjdk --iterations=1 --aotIterations= --testFlag= --testTarget=extended.openjdk --testList= --numOfMachines= --testTime=120 --TRSSURL= [2025-06-26T21:21:48.432Z] Modes data parsed from resources/modes.xml and resources/ottawa.csv. [2025-06-26T21:21:48.432Z] [2025-06-26T21:21:48.432Z] [2025-06-26T21:21:48.432Z] Starting to generate parallel test lists. [2025-06-26T21:21:48.432Z] [2025-06-26T21:21:48.788Z] Parsing C:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests\TKG\..\openjdk\playlist.xml [2025-06-26T21:21:48.788Z] Attempting to get test duration data from TRSS. [2025-06-26T21:21:48.788Z] cmd.exe /c curl --silent --max-time 120 -L -k "https://trss.adoptopenjdk.net/api/getTestAvgDuration?limit=10&jdkVersion=8&impl=hs&platform=x86-64_windows&group=openjdk&level=extended" [2025-06-26T21:21:49.128Z] Attempting to get test duration data from cached files. [2025-06-26T21:21:49.128Z] Reading file: Test_openjdk8_hs_openjdk_x86-64_windows.json [2025-06-26T21:21:49.128Z] Warning: cannot get data from cached files. [2025-06-26T21:21:49.128Z] [2025-06-26T21:21:49.128Z] TEST DURATION [2025-06-26T21:21:49.128Z] ==================================================================================== [2025-06-26T21:21:49.128Z] Total number of tests searched: 64 [2025-06-26T21:21:49.128Z] Number of test durations found: 64 [2025-06-26T21:21:49.128Z] Top slowest tests: [2025-06-26T21:21:49.128Z] 20m29s hotspot_jdk_0 [2025-06-26T21:21:49.128Z] 12m26s jdk_jfr_1 [2025-06-26T21:21:49.128Z] 12m18s jdk_jfr_0 [2025-06-26T21:21:49.128Z] ==================================================================================== [2025-06-26T21:21:49.128Z] [2025-06-26T21:21:49.128Z] Test target is split into 2 lists. [2025-06-26T21:21:49.128Z] Reducing estimated test running time from 168m24s to 118m17s. [2025-06-26T21:21:49.128Z] [2025-06-26T21:21:49.128Z] -------------------------------------testList_0------------------------------------- [2025-06-26T21:21:49.128Z] Number of tests: 12 [2025-06-26T21:21:49.128Z] Estimated running time: 118m17s [2025-06-26T21:21:49.128Z] TESTLIST=hotspot_jdk_0,jdk_jfr_1,jdk_jfr_0,jdk_other_0,jdk_other_1,jdk_net_0,jdk_net_1,jdk_nio_0,jdk_nio_1,jdk_rmi_1,jdk_beans_0,jdk_rmi_0 [2025-06-26T21:21:49.128Z] ------------------------------------------------------------------------------------ [2025-06-26T21:21:49.128Z] [2025-06-26T21:21:49.128Z] -------------------------------------testList_1------------------------------------- [2025-06-26T21:21:49.128Z] Number of tests: 52 [2025-06-26T21:21:49.128Z] Estimated running time: 50m06s [2025-06-26T21:21:49.128Z] TESTLIST=jdk_beans_1,jdk_tools_0,jdk_tools_1,jdk_jmx_0,jdk_jmx_1,jdk_instrument_0,jdk_instrument_1,jdk_time_0,jdk_imageio_1,jdk_time_1,jdk_imageio_0,jdk_io_0,jdk_io_1,jdk_management_0,jdk_management_1,jdk_text_0,jdk_text_1,jdk_2d_0,jdk_2d_2,jdk_security_infra_1,jdk_2d_1,jdk_swing_1,jdk_awt_1,jdk_security_infra_2,jdk_security3_1,jdk_security3_2,jdk_sound_0,jdk_swing_2,jdk_security_infra_0,jdk_awt_2,jdk_sound_1,jdk_swing_0,jdk_sound_2,jdk_security3_0,jdk_io_2,jdk_awt_0,jdk_rmi_2,jdk_security_infra_zos_0,jdk_security_infra_zos_1,jdk_jfr_2,jdk_security_infra_zos_2,jdk_imageio_2,jdk_time_2,jdk_net_2,jdk_other_2,jdk_tools_2,jdk_nio_2,jdk_beans_2,jdk_management_2,jdk_instrument_2,jdk_text_2,jdk_jmx_2 [2025-06-26T21:21:49.128Z] ------------------------------------------------------------------------------------ [2025-06-26T21:21:49.128Z] [2025-06-26T21:21:49.128Z] Parallel test lists file (C:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests\TKG/../TKG/parallelList.mk) is generated successfully. [2025-06-26T21:21:49.128Z] make[1]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows/aqa-tests/TKG' [Pipeline] fileExists [Pipeline] echo [2025-06-26T21:21:49.215Z] read parallelList.mk file: aqa-tests/TKG/parallelList.mk [Pipeline] readProperties [Pipeline] echo [2025-06-26T21:21:49.296Z] Saving parallelList.mk file on jenkins... [Pipeline] dir [2025-06-26T21:21:49.298Z] Running in c:\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows\aqa-tests\TKG [Pipeline] { [Pipeline] archiveArtifacts [2025-06-26T21:21:49.334Z] Archiving artifacts [2025-06-26T21:21:49.381Z] Recording fingerprints [Pipeline] } [Pipeline] // dir [Pipeline] echo [2025-06-26T21:21:49.440Z] [PARALLEL: Dynamic] childJobNum is 2, 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] echo [2025-06-26T21:21:49.808Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0 params for generating the job [Pipeline] echo [2025-06-26T21:21:49.810Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1 params for generating the job [Pipeline] fileExists [Pipeline] fileExists [Pipeline] jobDsl [Pipeline] jobDsl [2025-06-26T21:21:49.954Z] Processing DSL script aqa-tests/buildenv/jenkins/testJobTemplate [2025-06-26T21:21:49.954Z] Processing DSL script aqa-tests/buildenv/jenkins/testJobTemplate [2025-06-26T21:22:29.134Z] LEVELS: [extended] [2025-06-26T21:22:29.140Z] JDK_VERSIONS: [8] [2025-06-26T21:22:29.140Z] GROUPS: [openjdk] [2025-06-26T21:22:29.140Z] ARCH_OS_LIST: [x86-64_windows] [2025-06-26T21:22:29.239Z] LEVELS: [extended] [2025-06-26T21:22:29.249Z] JDK_VERSIONS: [8] [2025-06-26T21:22:29.249Z] GROUPS: [openjdk] [2025-06-26T21:22:29.249Z] ARCH_OS_LIST: [x86-64_windows] [2025-06-26T21:22:29.621Z] Existing items: [2025-06-26T21:22:29.621Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0'} [2025-06-26T21:22:29.621Z] Unreferenced items: [2025-06-26T21:22:29.621Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun'} [2025-06-26T21:22:29.621Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1'} [2025-06-26T21:22:29.628Z] Existing items: [2025-06-26T21:22:29.628Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0'} [2025-06-26T21:22:29.628Z] Unreferenced items: [2025-06-26T21:22:29.628Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun'} [2025-06-26T21:22:29.628Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1'} [Pipeline] } [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T21:22:42.122Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-26T21:22:42.590Z] + aqa-tests/terminateTestProcesses.sh null [2025-06-26T21:22:42.590Z] Windows machine, using powershell queries... [2025-06-26T21:22:43.303Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-26T21:22:43.417Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T21:22:43.417Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T21:22:45.165Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-26T21:22:45.669Z] + find /cygdrive/c/temp -name '*core*' -print -exec rm -f '{}' ';' [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-26T21:22:45.764Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T21:22:45.891Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [Pipeline] { (Branch: testList_0) [Pipeline] { (Branch: testList_1) [Pipeline] build [2025-06-26T21:22:45.944Z] Scheduling project: Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0 [Pipeline] build [2025-06-26T21:22:45.951Z] Scheduling project: Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1 [2025-06-26T21:22:51.936Z] Starting building: Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0 #33 [2025-06-26T21:22:51.938Z] Starting building: Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1 #33 [2025-06-26T22:17:19.220Z] Build Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1 #33 completed: SUCCESS [Pipeline] } [2025-06-26T23:21:45.374Z] Build Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0 #33 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-26T23:21:45.512Z] Running on test-rise-ubuntu2404-riscv64-9 in /home/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows [Pipeline] { [Pipeline] cleanWs [2025-06-26T23:21:45.583Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T23:21:45.584Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T23:21:45.607Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-26T23:21:45.614Z] Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1 #33 completed with status SUCCESS [Pipeline] timeout [2025-06-26T23:21:45.620Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-26T23:21:45.833Z] Copied 1 artifact from "Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1" build number 33 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-26T23:21:45.906Z] TAP Reports Processing: START [2025-06-26T23:21:45.906Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1/33/**/*.tap [2025-06-26T23:21:45.943Z] Saving reports... [2025-06-26T23:21:45.987Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.openjdk_x86-64_windows/builds/223/tap-master-files/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1/33/aqa-tests/TKG/output_17509733629096/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1.tap' [2025-06-26T23:21:45.987Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.openjdk_x86-64_windows/builds/223/tap-master-files/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1/33/aqa-tests/TKG/output_17509733629096/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1.tap]. [2025-06-26T23:21:45.993Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-26T23:21:46.001Z] Saving Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1/33/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T23:21:46.034Z] Archiving artifacts [2025-06-26T23:21:46.122Z] Recording fingerprints [Pipeline] echo [2025-06-26T23:21:46.181Z] Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0 #33 completed with status UNSTABLE [Pipeline] timeout [2025-06-26T23:21:46.183Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-26T23:21:46.377Z] Copied 1 artifact from "Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0" build number 33 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-26T23:21:46.457Z] TAP Reports Processing: START [2025-06-26T23:21:46.458Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0/33/**/*.tap [2025-06-26T23:21:46.488Z] Saving reports... [2025-06-26T23:21:46.523Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.openjdk_x86-64_windows/builds/223/tap-master-files/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0/33/aqa-tests/TKG/output_17509734085668/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0.tap' [2025-06-26T23:21:46.523Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.openjdk_x86-64_windows/builds/223/tap-master-files/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0/33/aqa-tests/TKG/output_17509734085668/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0.tap]. [2025-06-26T23:21:46.528Z] There are failed test cases. Marking build as UNSTABLE [2025-06-26T23:21:46.552Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-26T23:21:46.568Z] Saving Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0/33/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T23:21:46.607Z] Archiving artifacts [2025-06-26T23:21:46.688Z] 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. [Pipeline] findFiles [Pipeline] echo [2025-06-26T23:21:47.272Z] Tap file found: Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1/33/aqa-tests/TKG/output_17509733629096/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1.tap... [Pipeline] readFile [Pipeline] findFiles [Pipeline] echo [2025-06-26T23:21:47.494Z] Tap file found: Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0/33/aqa-tests/TKG/output_17509734085668/Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0.tap... [Pipeline] readFile [Pipeline] echo [2025-06-26T23:21:47.657Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=hotspot_jdk_0,jdk_other_0,jdk_other_1,jdk_net_0,jdk_net_1,jdk_nio_0,jdk_nio_1,jdk_rmi_0,jdk_rmi_1,jdk_jfr_0,jdk_jfr_1&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=5&VENDOR_TEST_DIRS=&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=x86-64_windows&GENERATE_JOBS=true&KEEP_REPORTDIR=true&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=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%2Fjdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-windows-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk8u462-b07_adopt&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=openjdk&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=564&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] echo [2025-06-26T23:21:47.702Z] Rerun failed jdk test cases in Grinder with jdk_custom target: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=jdk_custom&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=5&VENDOR_TEST_DIRS=&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=x86-64_windows&GENERATE_JOBS=true&KEEP_REPORTDIR=true&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=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%2Fjdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-windows-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=com%2Fsun%2Fcorba%2FcachedSocket%2F7056731.sh+com%2Fsun%2Fcorba%2F5036554%2FTestCorbaBug.sh+demo%2Fzipfs%2Fbasic.sh+javax%2Frmi%2Fssl%2FSSLSocketParametersTest.sh+javax%2Fscript%2FProviderTest.sh+javax%2Fxml%2Fjaxp%2Fcommon%2F8035437%2Frun.sh+javax%2Fxml%2Fws%2Fxsanymixed%2FTest.java+com%2Foracle%2Fnet%2Fsanity.sh+java%2Fnet%2FAuthenticator%2FB4933582.sh+java%2Fnet%2FDatagramSocket%2FSetDatagramSocketImplFactory%2FADatagramSocket.java+java%2Fnet%2FInetAddress%2Fptr%2Flookup.sh+java%2Fnet%2FServerSocket%2FAcceptCauseFileDescriptorLeak.sh+java%2Fnet%2FSocket%2FOldSocketImpl.sh+java%2Fnet%2FURL%2FB5086147.java+java%2Fnet%2FURLClassLoader%2Fclosetest%2FCloseTest.java+java%2Fnet%2FURLClassLoader%2Fclosetest%2FGetResourceAsStream.java+java%2Fnet%2FURLClassLoader%2Fgetresourceasstream%2Ftest.sh+java%2Fnet%2FURLClassLoader%2Fsealing%2FCheckSealed.java+java%2Fnet%2FURLClassLoader%2FB5077773.sh+java%2Fnet%2FURLConnection%2F6212146%2Ftest.sh+java%2Fnet%2FURLConnection%2FUNCTest.sh+java%2Fnet%2FURLPermission%2Fnstest%2Flookup.sh+sun%2Fnet%2Fftp%2FMarkResetTest.sh+sun%2Fnet%2FInetAddress%2Fnameservice%2Fdns%2Fcname.sh+sun%2Fnet%2Fsdp%2Fsanity.sh+sun%2Fnet%2Fwww%2Fhttp%2FHttpClient%2FRetryPost.sh+sun%2Fnet%2Fwww%2Fprotocol%2Ffile%2FDirPermissionDenied.sh+sun%2Fnet%2Fwww%2Fprotocol%2Fjar%2Fjarbug%2Frun.sh+sun%2Fnet%2Fwww%2Fprotocol%2Fjar%2FB5105410.sh+sun%2Fnet%2Fwww%2Fprotocol%2Fjar%2FB6449504.java+sun%2Fnet%2Fwww%2Fprotocol%2Fjar%2FGetContentType.java+java%2Fnio%2FBuffer%2FLimitDirectMemory.sh+java%2Fnio%2Fchannels%2FAsynchronousChannelGroup%2Frun_any_task.sh+java%2Fnio%2Fchannels%2FSelector%2Flots_of_updates.sh+java%2Fnio%2Fchannels%2FSocketChannel%2FOpen.java+java%2Fnio%2Fchannels%2Fspi%2FAsynchronousChannelProvider%2Fcustom_provider.sh+java%2Fnio%2Fchannels%2Fspi%2FSelectorProvider%2FinheritedChannel%2Frun_tests.sh+java%2Fnio%2Fcharset%2FCharset%2Fdefault.sh+java%2Fnio%2Fcharset%2Fcoders%2FCheckSJISMappingProp.sh+java%2Fnio%2Fcharset%2Fspi%2Fbasic.sh+java%2Fnio%2Ffile%2FFiles%2FwalkFileTree%2Ffind.sh+java%2Fnio%2Ffile%2FFiles%2Fdelete_on_close.sh+java%2Fnio%2Ffile%2FPath%2FMacPathTest.java+sun%2Fnio%2Fcs%2FTest4200310.sh+java%2Frmi%2Factivation%2FActivatable%2FextLoadedImpl%2Fext.sh+java%2Frmi%2Fregistry%2FreadTest%2FreadTest.sh+sun%2Frmi%2Frmic%2FclassFileVersion%2Frun.sh+sun%2Frmi%2Frmic%2FcovariantReturns%2Frun.sh+sun%2Frmi%2Frmic%2FextraCompilation%2Frun.sh+sun%2Frmi%2Frmic%2FmanifestClassPath%2Frun.sh+sun%2Frmi%2Frmic%2FdefaultStubVersion%2Frun.sh+sun%2Frmi%2Frmic%2FminimizeWrapperInstances%2Frun.sh+sun%2Frmi%2Frmic%2Fnewrmic%2Fequivalence%2Frun.sh+java%2Frmi%2Factivation%2FActivatable%2FextLoadedImpl%2Fext.sh+java%2Frmi%2Fregistry%2FreadTest%2FreadTest.sh+sun%2Frmi%2Frmic%2FclassFileVersion%2Frun.sh+sun%2Frmi%2Frmic%2FcovariantReturns%2Frun.sh+sun%2Frmi%2Frmic%2FdefaultStubVersion%2Frun.sh+sun%2Frmi%2Frmic%2FextraCompilation%2Frun.sh+sun%2Frmi%2Frmic%2FmanifestClassPath%2Frun.sh+sun%2Frmi%2Frmic%2FminimizeWrapperInstances%2Frun.sh+sun%2Frmi%2Frmic%2Fnewrmic%2Fequivalence%2Frun.sh+jdk%2Fjfr%2Fevent%2Fgc%2Fconfiguration%2FTestGCHeapConfigurationEventWithHeapBasedOops.sh+jdk%2Fjfr%2Fevent%2Fgc%2Fconfiguration%2FTestGCHeapConfigurationEventWith32BitOops.sh+jdk%2Fjfr%2Fevent%2Fgc%2Fconfiguration%2FTestGCHeapConfigurationEventWithZeroBasedOops.sh+jdk%2Fjfr%2Fevent%2Fio%2FEvilInstrument.java+jdk%2Fjfr%2Fevent%2Fos%2FTestInitialEnvironmentVariable.sh+jdk%2Fjfr%2Fevent%2Fruntime%2FTestVMInfoEvent.sh+jdk%2Fjfr%2Fevent%2Fsampling%2FTestNative.java+jdk%2Fjfr%2Fevent%2Fgc%2Fconfiguration%2FTestGCHeapConfigurationEventWith32BitOops.sh+jdk%2Fjfr%2Fevent%2Fgc%2Fconfiguration%2FTestGCHeapConfigurationEventWithZeroBasedOops.sh+jdk%2Fjfr%2Fevent%2Fgc%2Fconfiguration%2FTestGCHeapConfigurationEventWithHeapBasedOops.sh+jdk%2Fjfr%2Fevent%2Fio%2FEvilInstrument.java+jdk%2Fjfr%2Fevent%2Fos%2FTestInitialEnvironmentVariable.sh+jdk%2Fjfr%2Fevent%2Fruntime%2FTestVMInfoEvent.sh+jdk%2Fjfr%2Fevent%2Fsampling%2FTestNative.java&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk8u462-b07_adopt&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=openjdk&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=564&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] echo [2025-06-26T23:21:47.734Z] Rerun failed hotspot test cases in Grinder with hotspot_custom target: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=hotspot_custom&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=5&VENDOR_TEST_DIRS=&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=x86-64_windows&GENERATE_JOBS=true&KEEP_REPORTDIR=true&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=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%2Fjdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-windows-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=runtime%2F7107135%2FTest7107135.sh+compiler%2F5091921%2FTest6890943.java+compiler%2F5091921%2FTest7005594.java+compiler%2F6894807%2FIsInstanceTest.java+compiler%2F7068051%2FTest7068051.java+compiler%2F7070134%2FStemmer.java+compiler%2F7200264%2FTestIntVect.java+compiler%2FciReplay%2FTestSA.sh+compiler%2FciReplay%2FTestVM_no_comp_level.sh+compiler%2FciReplay%2FTestVM.sh+compiler%2Fcriticalnatives%2Fargumentcorruption%2FTest8167409.sh+compiler%2Ffloatingpoint%2F8165673%2FTestFloatJNIArgs.sh+compiler%2Ffloatingpoint%2F8207838%2FTestFloatSyncJNIArgs.sh+compiler%2Fnative%2FTestDirtyInt.sh+runtime%2F6888954%2Fvmerrors.sh+runtime%2F7110720%2FTest7110720.sh+runtime%2F7162488%2FTest7162488.sh+runtime%2Fjni%2FCallWithJNIWeak%2Ftest.sh+runtime%2Fjni%2FReturnJNIWeak%2Ftest.sh+runtime%2FStackGap%2Ftestme.sh+serviceability%2F7170638%2FSDTProbesGNULinuxTest.sh&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk8u462-b07_adopt&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=openjdk&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=564&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] cleanWs [2025-06-26T23:21:48.063Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T23:21:48.063Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T23:21:48.106Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-26T23:21:48.223Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-26T23:21:48.302Z] Running on test-azure-win11-aarch64-3 in C:\Users\jenkins\workspace\Test_openjdk8_hs_extended.openjdk_x86-64_windows [Pipeline] { [Pipeline] echo [2025-06-26T23:21:48.333Z] Generating rerun Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun) [Pipeline] echo [2025-06-26T23:21:48.378Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-06-26T23:21:49.221Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-26T23:21:50.841Z] Processing DSL script testJobTemplate [2025-06-26T23:22:17.264Z] LEVELS: [extended] [2025-06-26T23:22:17.264Z] JDK_VERSIONS: [8] [2025-06-26T23:22:17.264Z] GROUPS: [openjdk] [2025-06-26T23:22:17.264Z] ARCH_OS_LIST: [x86-64_windows] [2025-06-26T23:22:17.511Z] Existing items: [2025-06-26T23:22:17.511Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun'} [2025-06-26T23:22:17.511Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_0'} [2025-06-26T23:22:17.511Z] Unreferenced items: [2025-06-26T23:22:17.512Z] GeneratedJob{name='Test_openjdk8_hs_extended.openjdk_x86-64_windows_testList_1'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-26T23:22:42.101Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun) [Pipeline] build [2025-06-26T23:22:42.134Z] Scheduling project: Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun [2025-06-26T23:22:48.337Z] Starting building: Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun #27 [2025-06-27T01:05:19.387Z] Build Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun #27 completed: SUCCESS [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-27T01:05:19.556Z] Running on test-osuosl-aix72-ppc64-2 in /home/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_x86-64_windows [Pipeline] { [Pipeline] cleanWs [2025-06-27T01:05:19.910Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T01:05:19.910Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T01:05:20.076Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-27T01:05:20.083Z] Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun #27 completed with status SUCCESS [Pipeline] timeout [2025-06-27T01:05:20.085Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-27T01:05:21.105Z] Copied 1 artifact from "Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun" build number 27 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-27T01:05:21.318Z] TAP Reports Processing: START [2025-06-27T01:05:21.318Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun/27/**/*.tap [2025-06-27T01:05:21.485Z] Saving reports... [2025-06-27T01:05:21.657Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.openjdk_x86-64_windows/builds/223/tap-master-files/Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun/27/aqa-tests/TKG/output_17509803523013/Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun.tap' [2025-06-27T01:05:21.657Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.openjdk_x86-64_windows/builds/223/tap-master-files/Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun/27/aqa-tests/TKG/output_17509803523013/Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun.tap]. [2025-06-27T01:05:21.681Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-27T01:05:21.690Z] Saving Test_openjdk8_hs_extended.openjdk_x86-64_windows_rerun/27/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T01:05:21.867Z] Archiving artifacts [2025-06-27T01:05:22.206Z] 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. [Pipeline] cleanWs [2025-06-27T01:05:23.645Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T01:05:23.645Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T01:05:23.812Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE