[2025-06-12T21:57:31.220Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/system/reproducibleCompare' [2025-06-12T21:57:31.220Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/system' [2025-06-12T21:57:31.220Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests' [2025-06-12T21:57:31.220Z] [2025-06-12T21:57:31.220Z] [2025-06-12T21:57:31.220Z] All tests finished, run result summary: [2025-06-12T21:57:31.220Z] cd "/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-06-12T21:57:31.220Z] 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_17497653781843/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_17497653781843/ --tapName=Test_openjdk25_hs_special.system_aarch64_linux.tap --comment="" [2025-06-12T21:57:31.220Z] [2025-06-12T21:57:31.220Z] [2025-06-12T21:57:31.220Z] TEST TARGETS SUMMARY [2025-06-12T21:57:31.220Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-12T21:57:31.220Z] PASSED test targets: [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] system_custom_0 [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] MachineInfo_0 [2025-06-12T21:57:31.220Z] [2025-06-12T21:57:31.220Z] FAILED test targets: [2025-06-12T21:57:31.220Z] Rebuild_Same_JDK_Reproducibility_Test_0 [2025-06-12T21:57:31.220Z] [2025-06-12T21:57:31.220Z] TOTAL: 13 EXECUTED: 11 PASSED: 10 FAILED: 1 DISABLED: 0 SKIPPED: 2 [2025-06-12T21:57:31.220Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-12T21:57:31.220Z] [2025-06-12T21:57:31.220Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-12T21:57:31.220Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux/aqa-tests/TKG' [2025-06-12T21:57:31.220Z] make: *** [makefile:62: _special.system] Error 2 [Pipeline] sh [2025-06-12T21:57:34.154Z] + uname [2025-06-12T21:57:34.154Z] + [ Linux = AIX ] [2025-06-12T21:57:34.154Z] + uname [2025-06-12T21:57:34.154Z] + [ Linux = SunOS ] [2025-06-12T21:57:34.154Z] + uname [2025-06-12T21:57:34.154Z] + [ Linux = *BSD ] [2025-06-12T21:57:34.154Z] + MAKE=make [2025-06-12T21:57:34.154Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-12T21:57:34.154Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-12T21:57:34.663Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-06-12T21:57:35.351Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-12T21:57:35.662Z] TAP Reports Processing: START [2025-06-12T21:57:35.663Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-12T21:57:35.917Z] Saving reports... [2025-06-12T21:57:36.095Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/15/tap-master-files/aqa-tests/TKG/output_17497653781843/Test_openjdk25_hs_special.system_aarch64_linux.tap' [2025-06-12T21:57:36.095Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/15/tap-master-files/aqa-tests/TKG/output_17497653781843/Test_openjdk25_hs_special.system_aarch64_linux.tap]. [2025-06-12T21:57:36.097Z] There are failed test cases. Marking build as UNSTABLE [2025-06-12T21:57:36.097Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-12T21:57:36.119Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-12T21:57:36.323Z] Archiving artifacts [2025-06-12T21:57:36.679Z] Recording fingerprints [Pipeline] echo [2025-06-12T21:57:36.879Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-12T21:57:37.061Z] Archiving artifacts [2025-06-12T21:57:37.434Z] Recording fingerprints [Pipeline] sh [2025-06-12T21:57:39.652Z] + tar -cf - ./aqa-tests/TKG/output_17497653781843 [2025-06-12T21:57:39.652Z] + pigz -9 [Pipeline] echo [2025-06-12T21:57:40.165Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-12T21:57:40.350Z] Archiving artifacts [2025-06-12T21:57:40.703Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-12T21:57:41.784Z] Tap file found: aqa-tests/TKG/output_17497653781843/Test_openjdk25_hs_special.system_aarch64_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-06-12T21:57:42.087Z] 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%2B27_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=423&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-12T21:57:42.272Z] Recording test results [2025-06-12T21:57:42.748Z] None of the test reports contained any result [2025-06-12T21:57:42.749Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-12T21:57:42.779Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-12T21:57:42.599Z] No test report files were found. Configuration error? [2025-06-12T21:57:44.740Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-06-12T21:57:44.740Z] Unix type machine.. [2025-06-12T21:57:44.740Z] Running on a Linux host [2025-06-12T21:57:44.740Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-12T21:57:45.605Z] [WS-CLEANUP] Deleting project workspace... [2025-06-12T21:57:45.605Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-12T21:57:46.736Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-12T21:57:48.717Z] + find /tmp -name *core* -print -exec rm -f {} ; [2025-06-12T21:57:49.654Z] + true [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-12T21:57:50.226Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-12T21:57:50.507Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-12T21:57:50.543Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-12T21:57:50.614Z] Running on test-osuosl-centos74-ppc64le-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] cleanWs [2025-06-12T21:57:50.982Z] [WS-CLEANUP] Deleting project workspace... [2025-06-12T21:57:50.982Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-12T21:57:51.162Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-12T21:57:51.711Z] [WS-CLEANUP] Deleting project workspace... [2025-06-12T21:57:51.711Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-12T21:57:51.887Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-12T21:57:51.981Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-12T21:57:52.039Z] Running on test-docker-ubuntu2404-armv7-3 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] echo [2025-06-12T21:57:52.063Z] 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-12T21:57:52.088Z] 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-12T21:57:53.831Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-12T21:57:54.886Z] Processing DSL script testJobTemplate [2025-06-12T22:01:23.494Z] LEVELS: [special] [2025-06-12T22:01:23.494Z] JDK_VERSIONS: [8] [2025-06-12T22:01:23.494Z] GROUPS: [system] [2025-06-12T22:01:23.494Z] ARCH_OS_LIST: [aarch64_linux] [2025-06-12T22:01:23.750Z] Existing items: [2025-06-12T22:01:23.750Z] GeneratedJob{name='Test_openjdk25_hs_special.system_aarch64_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-12T22:01:32.264Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.system_aarch64_linux_rerun) [Pipeline] build [2025-06-12T22:01:32.287Z] Scheduling project: Test_openjdk25_hs_special.system_aarch64_linux_rerun [2025-06-12T22:01:40.900Z] Starting building: Test_openjdk25_hs_special.system_aarch64_linux_rerun #8 [2025-06-13T00:47:03.071Z] Build Test_openjdk25_hs_special.system_aarch64_linux_rerun #8 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-13T00:47:03.226Z] Running on test-docker-ubi8-armv8-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.system_aarch64_linux [Pipeline] { [Pipeline] cleanWs [2025-06-13T00:47:03.517Z] [WS-CLEANUP] Deleting project workspace... [2025-06-13T00:47:03.517Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-13T00:47:03.645Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-13T00:47:03.654Z] Test_openjdk25_hs_special.system_aarch64_linux_rerun #8 completed with status UNSTABLE [Pipeline] timeout [2025-06-13T00:47:03.657Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-13T00:47:04.465Z] Copied 1 artifact from "Test_openjdk25_hs_special.system_aarch64_linux_rerun" build number 8 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-13T00:47:04.652Z] TAP Reports Processing: START [2025-06-13T00:47:04.653Z] Looking for TAP results report in workspace using pattern: Test_openjdk25_hs_special.system_aarch64_linux_rerun/8/**/*.tap [2025-06-13T00:47:04.782Z] Saving reports... [2025-06-13T00:47:04.914Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/15/tap-master-files/Test_openjdk25_hs_special.system_aarch64_linux_rerun/8/aqa-tests/TKG/output_17497756044498/Test_openjdk25_hs_special.system_aarch64_linux_rerun.tap' [2025-06-13T00:47:04.914Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.system_aarch64_linux/builds/15/tap-master-files/Test_openjdk25_hs_special.system_aarch64_linux_rerun/8/aqa-tests/TKG/output_17497756044498/Test_openjdk25_hs_special.system_aarch64_linux_rerun.tap]. [2025-06-13T00:47:04.916Z] There are failed test cases. Marking build as UNSTABLE [2025-06-13T00:47:04.935Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-13T00:47:04.943Z] Saving Test_openjdk25_hs_special.system_aarch64_linux_rerun/8/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-13T00:47:05.080Z] Archiving artifacts [2025-06-13T00:47:05.340Z] 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-13T00:47:06.447Z] [WS-CLEANUP] Deleting project workspace... [2025-06-13T00:47:06.447Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-13T00:47:06.576Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE