[2025-05-28T20:24:53.516Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests/system/reproducibleCompare' [2025-05-28T20:24:53.517Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests/system' [2025-05-28T20:24:53.517Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests' [2025-05-28T20:24:53.517Z] [2025-05-28T20:24:53.517Z] [2025-05-28T20:24:53.517Z] All tests finished, run result summary: [2025-05-28T20:24:53.517Z] cd "/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-05-28T20:24:53.517Z] perl "resultsSum.pl" --failuremk="/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/failedtargets.mk" --resultFile="/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/output_17484638398451/TestTargetResult" --platFile="/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/resources/buildPlatformMap.properties" --diagnostic=failure --jdkVersion=21 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=linux_aarch64 --buildList=system --customTarget="" --testTarget=special.system --tapPath=/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/output_17484638398451/ --tapName=Test_openjdk21_hs_special.system_aarch64_linux.tap --comment="" [2025-05-28T20:24:53.517Z] [2025-05-28T20:24:53.517Z] [2025-05-28T20:24:53.517Z] TEST TARGETS SUMMARY [2025-05-28T20:24:53.517Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-05-28T20:24:53.517Z] PASSED test targets: [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] system_custom_0 [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] MachineInfo_0 [2025-05-28T20:24:53.517Z] [2025-05-28T20:24:53.517Z] FAILED test targets: [2025-05-28T20:24:53.517Z] Rebuild_Same_JDK_Reproducibility_Test_0 [2025-05-28T20:24:53.517Z] [2025-05-28T20:24:53.517Z] TOTAL: 13 EXECUTED: 11 PASSED: 10 FAILED: 1 DISABLED: 0 SKIPPED: 2 [2025-05-28T20:24:53.517Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-05-28T20:24:53.517Z] [2025-05-28T20:24:53.517Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-05-28T20:24:53.517Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux/aqa-tests/TKG' [2025-05-28T20:24:53.517Z] make: *** [makefile:62: _special.system] Error 2 [Pipeline] sh [2025-05-28T20:24:56.031Z] + uname [2025-05-28T20:24:56.031Z] + [ Linux = AIX ] [2025-05-28T20:24:56.031Z] + uname [2025-05-28T20:24:56.031Z] + [ Linux = SunOS ] [2025-05-28T20:24:56.031Z] + uname [2025-05-28T20:24:56.031Z] + [ Linux = *BSD ] [2025-05-28T20:24:56.031Z] + MAKE=make [2025-05-28T20:24:56.031Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-05-28T20:24:56.031Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-05-28T20:24:56.552Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-05-28T20:24:57.181Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-05-28T20:24:57.448Z] TAP Reports Processing: START [2025-05-28T20:24:57.449Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-05-28T20:24:57.647Z] Saving reports... [2025-05-28T20:24:57.826Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_special.system_aarch64_linux/builds/28/tap-master-files/aqa-tests/TKG/output_17484638398451/Test_openjdk21_hs_special.system_aarch64_linux.tap' [2025-05-28T20:24:57.826Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_special.system_aarch64_linux/builds/28/tap-master-files/aqa-tests/TKG/output_17484638398451/Test_openjdk21_hs_special.system_aarch64_linux.tap]. [2025-05-28T20:24:57.830Z] There are failed test cases. Marking build as UNSTABLE [2025-05-28T20:24:57.830Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-05-28T20:24:57.839Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-05-28T20:24:58.019Z] Archiving artifacts [2025-05-28T20:24:58.378Z] Recording fingerprints [Pipeline] echo [2025-05-28T20:24:58.576Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-05-28T20:24:58.758Z] Archiving artifacts [2025-05-28T20:24:59.132Z] Recording fingerprints [Pipeline] sh [2025-05-28T20:25:01.161Z] + tar -cf - ./aqa-tests/TKG/output_17484638398451 [2025-05-28T20:25:01.161Z] + pigz -9 [Pipeline] echo [2025-05-28T20:25:01.684Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-05-28T20:25:01.867Z] Archiving artifacts [2025-05-28T20:25:02.241Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-05-28T20:25:03.344Z] Tap file found: aqa-tests/TKG/output_17484638398451/Test_openjdk21_hs_special.system_aarch64_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-05-28T20:25:03.585Z] 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=21&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=https%3A%2F%2Fgithub.com%2Fadoptium%2Ftemurin-build&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=master&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk21u%2Fjdk21u-linux-aarch64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk-21.0.8%2B5_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=299&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-05-28T20:25:03.771Z] Recording test results [2025-05-28T20:25:04.192Z] None of the test reports contained any result [2025-05-28T20:25:04.194Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-05-28T20:25:04.236Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-05-28T20:25:04.038Z] No test report files were found. Configuration error? [2025-05-28T20:25:06.087Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-05-28T20:25:06.087Z] Unix type machine.. [2025-05-28T20:25:06.087Z] Running on a Linux host [2025-05-28T20:25:06.087Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-05-28T20:25:06.967Z] [WS-CLEANUP] Deleting project workspace... [2025-05-28T20:25:06.967Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-28T20:25:08.030Z] [WS-CLEANUP] done [Pipeline] sh [2025-05-28T20:25:10.033Z] + find /tmp -name *core* -print -exec rm -f {} ; [2025-05-28T20:25:10.033Z] + true [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-05-28T20:25:10.592Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-05-28T20:25:10.723Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-05-28T20:25:11.730Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-05-28T20:25:11.808Z] Running on test-azure-win11-aarch64-1 in C:\Users\jenkins\workspace\Test_openjdk21_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] cleanWs [2025-05-28T20:25:11.865Z] [WS-CLEANUP] Deleting project workspace... [2025-05-28T20:25:11.865Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-28T20:25:11.890Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-05-28T20:25:11.956Z] [WS-CLEANUP] Deleting project workspace... [2025-05-28T20:25:11.956Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-28T20:25:11.972Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-05-28T20:25:12.091Z] allocate a node for generating rerun job ... [Pipeline] node [2025-05-28T20:25:12.129Z] Running on test-macstadium-macos1014-x64-1 in /Users/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] echo [2025-05-28T20:25:12.148Z] Generating rerun Test_openjdk21_hs_special.system_aarch64_linux_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk21_hs_special.system_aarch64_linux_rerun) [Pipeline] echo [2025-05-28T20:25:12.181Z] GENERATE_JOBS is set to true, set test job Test_openjdk21_hs_special.system_aarch64_linux_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-05-28T20:25:12.758Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-05-28T20:25:12.960Z] Processing DSL script testJobTemplate [2025-05-28T20:25:57.000Z] LEVELS: [special] [2025-05-28T20:25:57.000Z] JDK_VERSIONS: [8] [2025-05-28T20:25:57.000Z] GROUPS: [system] [2025-05-28T20:25:57.000Z] ARCH_OS_LIST: [aarch64_linux] [2025-05-28T20:25:57.172Z] Added items: [2025-05-28T20:25:57.172Z] GeneratedJob{name='Test_openjdk21_hs_special.system_aarch64_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-05-28T20:25:58.164Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk21_hs_special.system_aarch64_linux_rerun) [Pipeline] build [2025-05-28T20:25:58.190Z] Scheduling project: Test_openjdk21_hs_special.system_aarch64_linux_rerun [2025-05-28T20:26:04.143Z] Starting building: Test_openjdk21_hs_special.system_aarch64_linux_rerun #16 [2025-05-28T23:09:48.380Z] Build Test_openjdk21_hs_special.system_aarch64_linux_rerun #16 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-05-28T23:09:48.470Z] Running on test-osuosl-centos74-ppc64le-1 in /home/jenkins/workspace/Test_openjdk21_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] cleanWs [2025-05-28T23:09:48.847Z] [WS-CLEANUP] Deleting project workspace... [2025-05-28T23:09:48.847Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-28T23:09:49.026Z] [WS-CLEANUP] done [Pipeline] echo [2025-05-28T23:09:49.035Z] Test_openjdk21_hs_special.system_aarch64_linux_rerun #16 completed with status UNSTABLE [Pipeline] timeout [2025-05-28T23:09:49.037Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-05-28T23:09:50.415Z] Copied 1 artifact from "Test_openjdk21_hs_special.system_aarch64_linux_rerun" build number 16 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-05-28T23:09:50.643Z] TAP Reports Processing: START [2025-05-28T23:09:50.644Z] Looking for TAP results report in workspace using pattern: Test_openjdk21_hs_special.system_aarch64_linux_rerun/16/**/*.tap [2025-05-28T23:09:50.820Z] Saving reports... [2025-05-28T23:09:51.173Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_special.system_aarch64_linux/builds/28/tap-master-files/Test_openjdk21_hs_special.system_aarch64_linux_rerun/16/aqa-tests/TKG/output_17484737684190/Test_openjdk21_hs_special.system_aarch64_linux_rerun.tap' [2025-05-28T23:09:51.173Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_special.system_aarch64_linux/builds/28/tap-master-files/Test_openjdk21_hs_special.system_aarch64_linux_rerun/16/aqa-tests/TKG/output_17484737684190/Test_openjdk21_hs_special.system_aarch64_linux_rerun.tap]. [2025-05-28T23:09:51.175Z] There are failed test cases. Marking build as UNSTABLE [2025-05-28T23:09:51.187Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-05-28T23:09:51.196Z] Saving Test_openjdk21_hs_special.system_aarch64_linux_rerun/16/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-05-28T23:09:51.379Z] Archiving artifacts [2025-05-28T23:09:51.737Z] 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-05-28T23:09:53.247Z] [WS-CLEANUP] Deleting project workspace... [2025-05-28T23:09:53.247Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-28T23:09:53.423Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE