[2025-06-07T21:57:38.959Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/system/reproducibleCompare' [2025-06-07T21:57:38.959Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/system' [2025-06-07T21:57:38.959Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests' [2025-06-07T21:57:38.959Z] [2025-06-07T21:57:38.959Z] [2025-06-07T21:57:38.959Z] All tests finished, run result summary: [2025-06-07T21:57:38.959Z] cd "/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-06-07T21:57:38.959Z] 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_17493334235865/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_17493334235865/ --tapName=Test_openjdk25_hs_special.system_aarch64_linux.tap --comment="" [2025-06-07T21:57:39.470Z] [2025-06-07T21:57:39.470Z] [2025-06-07T21:57:39.470Z] TEST TARGETS SUMMARY [2025-06-07T21:57:39.470Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-07T21:57:39.470Z] PASSED test targets: [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] system_custom_0 [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] MachineInfo_0 [2025-06-07T21:57:39.470Z] [2025-06-07T21:57:39.470Z] FAILED test targets: [2025-06-07T21:57:39.470Z] Rebuild_Same_JDK_Reproducibility_Test_0 [2025-06-07T21:57:39.470Z] [2025-06-07T21:57:39.470Z] TOTAL: 13 EXECUTED: 11 PASSED: 10 FAILED: 1 DISABLED: 0 SKIPPED: 2 [2025-06-07T21:57:39.470Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-07T21:57:39.470Z] [2025-06-07T21:57:39.470Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-07T21:57:39.470Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG' [2025-06-07T21:57:39.470Z] make: *** [makefile:62: _special.system] Error 2 [Pipeline] sh [2025-06-07T21:57:41.436Z] + uname [2025-06-07T21:57:41.436Z] + [ Linux = AIX ] [2025-06-07T21:57:41.436Z] + uname [2025-06-07T21:57:41.436Z] + [ Linux = SunOS ] [2025-06-07T21:57:41.436Z] + uname [2025-06-07T21:57:41.436Z] + [ Linux = *BSD ] [2025-06-07T21:57:41.436Z] + MAKE=make [2025-06-07T21:57:41.436Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-07T21:57:41.436Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-07T21:57:41.948Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-06-07T21:57:42.536Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-07T21:57:42.795Z] TAP Reports Processing: START [2025-06-07T21:57:42.796Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-07T21:57:43.030Z] Saving reports... [2025-06-07T21:57:43.385Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/14/tap-master-files/aqa-tests/TKG/output_17493334235865/Test_openjdk25_hs_special.system_aarch64_linux.tap' [2025-06-07T21:57:43.385Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/14/tap-master-files/aqa-tests/TKG/output_17493334235865/Test_openjdk25_hs_special.system_aarch64_linux.tap]. [2025-06-07T21:57:43.387Z] There are failed test cases. Marking build as UNSTABLE [2025-06-07T21:57:43.387Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-07T21:57:43.407Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-07T21:57:43.592Z] Archiving artifacts [2025-06-07T21:57:43.950Z] Recording fingerprints [Pipeline] echo [2025-06-07T21:57:44.139Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-07T21:57:44.317Z] Archiving artifacts [2025-06-07T21:57:44.677Z] Recording fingerprints [Pipeline] sh [2025-06-07T21:57:46.679Z] + tar -cf - ./aqa-tests/TKG/output_17493334235865 [2025-06-07T21:57:46.679Z] + pigz -9 [Pipeline] echo [2025-06-07T21:57:47.190Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-07T21:57:47.367Z] Archiving artifacts [2025-06-07T21:57:47.708Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-07T21:57:49.296Z] Tap file found: aqa-tests/TKG/output_17493334235865/Test_openjdk25_hs_special.system_aarch64_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-06-07T21:57:49.515Z] 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%2Fjdk%2Fjdk-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%2B26_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=422&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-07T21:57:49.698Z] Recording test results [2025-06-07T21:57:50.053Z] None of the test reports contained any result [2025-06-07T21:57:50.053Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-07T21:57:50.083Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-07T21:57:49.934Z] No test report files were found. Configuration error? [2025-06-07T21:57:52.047Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-06-07T21:57:52.047Z] Unix type machine.. [2025-06-07T21:57:52.047Z] Running on a Linux host [2025-06-07T21:57:52.047Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-07T21:57:52.912Z] [WS-CLEANUP] Deleting project workspace... [2025-06-07T21:57:52.913Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-07T21:57:53.912Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-07T21:57:55.888Z] + find /tmp -name *core* -print -exec rm -f {} ; [2025-06-07T21:57:55.888Z] + true [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-07T21:57:56.436Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-07T21:57:56.552Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-07T21:57:56.582Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-07T21:57:56.648Z] Running on test-osuosl-aix72-ppc64-5 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] cleanWs [2025-06-07T21:57:57.017Z] [WS-CLEANUP] Deleting project workspace... [2025-06-07T21:57:57.017Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-07T21:57:57.193Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-07T21:57:57.731Z] [WS-CLEANUP] Deleting project workspace... [2025-06-07T21:57:57.731Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-07T21:57:57.905Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-07T21:57:57.993Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-07T21:57:58.024Z] Running on test-marist-rhel7-s390x-2 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] echo [2025-06-07T21:57:58.041Z] 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-07T21:57:58.067Z] 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-07T21:57:59.614Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-07T21:58:00.441Z] Processing DSL script testJobTemplate [2025-06-07T22:00:39.641Z] LEVELS: [special] [2025-06-07T22:00:39.641Z] JDK_VERSIONS: [8] [2025-06-07T22:00:39.641Z] GROUPS: [system] [2025-06-07T22:00:39.641Z] ARCH_OS_LIST: [aarch64_linux] [2025-06-07T22:00:40.018Z] Existing items: [2025-06-07T22:00:40.018Z] GeneratedJob{name='Test_openjdk25_hs_special.system_aarch64_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-07T22:00:40.979Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.system_aarch64_linux_rerun) [Pipeline] build [2025-06-07T22:00:41.002Z] Scheduling project: Test_openjdk25_hs_special.system_aarch64_linux_rerun [2025-06-07T22:00:49.871Z] Starting building: Test_openjdk25_hs_special.system_aarch64_linux_rerun #7 [2025-06-08T00:32:19.117Z] Build Test_openjdk25_hs_special.system_aarch64_linux_rerun #7 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-08T00:32:19.236Z] Running on test-docker-ubuntu2404-armv7-4 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] cleanWs [2025-06-08T00:32:19.538Z] [WS-CLEANUP] Deleting project workspace... [2025-06-08T00:32:19.538Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-08T00:32:19.681Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-08T00:32:19.691Z] Test_openjdk25_hs_special.system_aarch64_linux_rerun #7 completed with status UNSTABLE [Pipeline] timeout [2025-06-08T00:32:19.694Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-08T00:32:20.705Z] Copied 1 artifact from "Test_openjdk25_hs_special.system_aarch64_linux_rerun" build number 7 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-08T00:32:20.908Z] TAP Reports Processing: START [2025-06-08T00:32:20.909Z] Looking for TAP results report in workspace using pattern: Test_openjdk25_hs_special.system_aarch64_linux_rerun/7/**/*.tap [2025-06-08T00:32:21.051Z] Saving reports... [2025-06-08T00:32:21.200Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/14/tap-master-files/Test_openjdk25_hs_special.system_aarch64_linux_rerun/7/aqa-tests/TKG/output_17493427159716/Test_openjdk25_hs_special.system_aarch64_linux_rerun.tap' [2025-06-08T00:32:21.200Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/14/tap-master-files/Test_openjdk25_hs_special.system_aarch64_linux_rerun/7/aqa-tests/TKG/output_17493427159716/Test_openjdk25_hs_special.system_aarch64_linux_rerun.tap]. [2025-06-08T00:32:21.202Z] There are failed test cases. Marking build as UNSTABLE [2025-06-08T00:32:21.223Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-08T00:32:21.234Z] Saving Test_openjdk25_hs_special.system_aarch64_linux_rerun/7/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-08T00:32:21.379Z] Archiving artifacts [2025-06-08T00:32:21.664Z] 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-08T00:32:22.888Z] [WS-CLEANUP] Deleting project workspace... [2025-06-08T00:32:22.888Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-08T00:32:23.029Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE