[2025-06-26T22:49:55.435Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/system/reproducibleCompare' [2025-06-26T22:49:55.435Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/system' [2025-06-26T22:49:55.435Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests' [2025-06-26T22:49:55.435Z] [2025-06-26T22:49:55.435Z] [2025-06-26T22:49:55.435Z] All tests finished, run result summary: [2025-06-26T22:49:55.435Z] cd "/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-06-26T22:49:55.435Z] perl "resultsSum.pl" --failuremk="/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/failedtargets.mk" --resultFile="/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/output_17509781617696/TestTargetResult" --platFile="/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/resources/buildPlatformMap.properties" --diagnostic=failure --jdkVersion=25 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=linux_aarch64 --buildList=system --customTarget="" --testTarget=special.system --tapPath=/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/output_17509781617696/ --tapName=Test_openjdk25_hs_special.system_aarch64_linux.tap --comment="" [2025-06-26T22:49:55.435Z] [2025-06-26T22:49:55.435Z] [2025-06-26T22:49:55.435Z] TEST TARGETS SUMMARY [2025-06-26T22:49:55.435Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-26T22:49:55.435Z] PASSED test targets: [2025-06-26T22:49:55.435Z] system_custom_0 [2025-06-26T22:49:55.435Z] [2025-06-26T22:49:55.435Z] FAILED test targets: [2025-06-26T22:49:55.435Z] Rebuild_Same_JDK_Reproducibility_Test_0 [2025-06-26T22:49:55.435Z] [2025-06-26T22:49:55.435Z] TOTAL: 4 EXECUTED: 2 PASSED: 1 FAILED: 1 DISABLED: 0 SKIPPED: 2 [2025-06-26T22:49:55.435Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-26T22:49:55.435Z] [2025-06-26T22:49:55.435Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-26T22:49:55.435Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG' [2025-06-26T22:49:55.435Z] make: *** [makefile:62: _special.system] Error 2 [Pipeline] sh [2025-06-26T22:49:57.956Z] + uname [2025-06-26T22:49:57.956Z] + [ Linux = AIX ] [2025-06-26T22:49:57.956Z] + uname [2025-06-26T22:49:57.956Z] + [ Linux = SunOS ] [2025-06-26T22:49:57.956Z] + uname [2025-06-26T22:49:57.956Z] + [ Linux = *BSD ] [2025-06-26T22:49:57.956Z] + MAKE=make [2025-06-26T22:49:57.956Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-26T22:49:57.956Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-26T22:49:58.563Z] $ ssh-agent -k [2025-06-26T22:49:58.569Z] unset SSH_AUTH_SOCK; [2025-06-26T22:49:58.570Z] unset SSH_AGENT_PID; [2025-06-26T22:49:58.570Z] echo Agent pid 245339 killed; [2025-06-26T22:49:59.376Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] } [2025-06-26T22:49:59.415Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-06-26T22:50:00.544Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-26T22:50:00.802Z] TAP Reports Processing: START [2025-06-26T22:50:00.803Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-26T22:50:01.009Z] Saving reports... [2025-06-26T22:50:01.189Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/17/tap-master-files/aqa-tests/TKG/output_17509781617696/Test_openjdk25_hs_special.system_aarch64_linux.tap' [2025-06-26T22:50:01.189Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/17/tap-master-files/aqa-tests/TKG/output_17509781617696/Test_openjdk25_hs_special.system_aarch64_linux.tap]. [2025-06-26T22:50:01.190Z] There are failed test cases. Marking build as UNSTABLE [2025-06-26T22:50:01.190Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-26T22:50:01.196Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T22:50:01.423Z] Archiving artifacts [2025-06-26T22:50:01.799Z] Recording fingerprints [Pipeline] echo [2025-06-26T22:50:02.051Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T22:50:02.258Z] Archiving artifacts [2025-06-26T22:50:02.634Z] Recording fingerprints [Pipeline] sh [2025-06-26T22:50:04.873Z] + tar -cf - ./aqa-tests/TKG/output_17509781617696 [2025-06-26T22:50:04.873Z] + pigz -9 [Pipeline] echo [2025-06-26T22:50:05.398Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-26T22:50:05.577Z] Archiving artifacts [2025-06-26T22:50:05.928Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-26T22:50:07.006Z] Tap file found: aqa-tests/TKG/output_17509781617696/Test_openjdk25_hs_special.system_aarch64_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-06-26T22:50:07.230Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=Rebuild_Same_JDK_Reproducibility_Test_0&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=5&VENDOR_TEST_DIRS=%2Ftest%2Fsystem&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=aarch64_linux&GENERATE_JOBS=true&KEEP_REPORTDIR=false&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=master&LIGHT_WEIGHT_CHECKOUT=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=25&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=https%3A%2F%2Fgithub.com%2Fadoptium%2Ftemurin-build&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=master&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk25%2Fjdk25-linux-aarch64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk-25%2B29_adopt&LABEL_ADDITION=sw.tool.docker&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=&TEST_TIME=120&JDK_IMPL=hotspot&SSH_AGENT_CREDENTIAL=&AUTO_DETECT=true&SLACK_CHANNEL=aqavit-bot&DYNAMIC_COMPILE=false&RELATED_NODES=&ADOPTOPENJDK_SYSTEMTEST_OWNER_BRANCH=adoptium%3Amaster&APPLICATION_OPTIONS=&CUSTOMIZED_SDK_URL_CREDENTIAL_ID=eclipse_temurin_bot_email_and_token&ARCHIVE_TEST_RESULTS=false&NUM_MACHINES=&OPENJDK_SHA=&TRSS_URL=&RERUN_FAILURE=false&USE_TESTENV_PROPERTIES=false&BUILD_LIST=system&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=3&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-26T22:50:07.422Z] Recording test results [2025-06-26T22:50:07.782Z] None of the test reports contained any result [2025-06-26T22:50:07.782Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T22:50:07.822Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-26T22:50:07.676Z] No test report files were found. Configuration error? [2025-06-26T22:50:09.818Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-06-26T22:50:09.818Z] Unix type machine.. [2025-06-26T22:50:09.818Z] Running on a Linux host [2025-06-26T22:50:09.818Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-26T22:50:10.698Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T22:50:10.698Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T22:50:11.752Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-26T22:50:13.602Z] + find /tmp -name *core* -print -exec rm -f {} ; [2025-06-26T22:50:13.603Z] + true [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-26T22:50:14.205Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T22:50:14.341Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-26T22:50:14.396Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-26T22:50:14.526Z] Running on test-docker-ubuntu2404-armv7-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] cleanWs [2025-06-26T22:50:14.908Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T22:50:14.908Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T22:50:15.084Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-26T22:50:15.651Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T22:50:15.651Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T22:50:15.827Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-26T22:50:16.006Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-26T22:50:16.058Z] Running on test-rise-ubuntu2404-riscv64-5 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] echo [2025-06-26T22:50:16.075Z] Generating rerun Test_openjdk25_hs_special.system_aarch64_linux_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.system_aarch64_linux_rerun) [Pipeline] echo [2025-06-26T22:50:16.115Z] GENERATE_JOBS is set to true, set test job Test_openjdk25_hs_special.system_aarch64_linux_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-06-26T22:50:16.801Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-26T22:50:17.031Z] Processing DSL script testJobTemplate [2025-06-26T22:51:08.335Z] LEVELS: [special] [2025-06-26T22:51:08.335Z] JDK_VERSIONS: [8] [2025-06-26T22:51:08.335Z] GROUPS: [system] [2025-06-26T22:51:08.335Z] ARCH_OS_LIST: [aarch64_linux] [2025-06-26T22:51:08.742Z] Existing items: [2025-06-26T22:51:08.742Z] GeneratedJob{name='Test_openjdk25_hs_special.system_aarch64_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-26T22:51:11.734Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.system_aarch64_linux_rerun) [Pipeline] build [2025-06-26T22:51:11.782Z] Scheduling project: Test_openjdk25_hs_special.system_aarch64_linux_rerun [2025-06-26T22:51:17.477Z] Starting building: Test_openjdk25_hs_special.system_aarch64_linux_rerun #10 [2025-06-27T02:38:29.467Z] Build Test_openjdk25_hs_special.system_aarch64_linux_rerun #10 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-27T02:38:29.636Z] Running on test-docker-ubuntu2404-armv8-3 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] cleanWs [2025-06-27T02:38:29.946Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T02:38:29.947Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T02:38:30.093Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-27T02:38:30.106Z] Test_openjdk25_hs_special.system_aarch64_linux_rerun #10 completed with status UNSTABLE [Pipeline] timeout [2025-06-27T02:38:30.109Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-27T02:38:30.979Z] Copied 1 artifact from "Test_openjdk25_hs_special.system_aarch64_linux_rerun" build number 10 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-27T02:38:31.186Z] TAP Reports Processing: START [2025-06-27T02:38:31.187Z] Looking for TAP results report in workspace using pattern: Test_openjdk25_hs_special.system_aarch64_linux_rerun/10/**/*.tap [2025-06-27T02:38:31.329Z] Saving reports... [2025-06-27T02:38:31.480Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/17/tap-master-files/Test_openjdk25_hs_special.system_aarch64_linux_rerun/10/aqa-tests/TKG/output_17509918906518/Test_openjdk25_hs_special.system_aarch64_linux_rerun.tap' [2025-06-27T02:38:31.480Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/17/tap-master-files/Test_openjdk25_hs_special.system_aarch64_linux_rerun/10/aqa-tests/TKG/output_17509918906518/Test_openjdk25_hs_special.system_aarch64_linux_rerun.tap]. [2025-06-27T02:38:31.482Z] There are failed test cases. Marking build as UNSTABLE [2025-06-27T02:38:31.498Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-27T02:38:31.509Z] Saving Test_openjdk25_hs_special.system_aarch64_linux_rerun/10/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T02:38:31.659Z] Archiving artifacts [2025-06-27T02:38:31.947Z] 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. [Pipeline] cleanWs [2025-06-27T02:38:33.173Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T02:38:33.173Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T02:38:33.339Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE