[2025-06-27T22:13:32.350Z] make[4]: Leaving directory '/cygdrive/c/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests/perf/renaissance' [2025-06-27T22:13:32.350Z] make[3]: Leaving directory '/cygdrive/c/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests/perf' [2025-06-27T22:13:32.350Z] make[2]: Leaving directory '/cygdrive/c/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests' [2025-06-27T22:13:32.350Z] [2025-06-27T22:13:32.350Z] [2025-06-27T22:13:32.650Z] All tests finished, run result summary: [2025-06-27T22:13:32.650Z] cd "C:/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests/\\TKG\\scripts"; \ [2025-06-27T22:13:32.650Z] perl "resultsSum.pl" --failuremk="C:/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests/\\TKG\\failedtargets.mk" --resultFile="C:/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests/\\TKG\\output_17510617532875\\TestTargetResult" --platFile="C:/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests/\\TKG\\resources\\buildPlatformMap.properties" --diagnostic=failure --jdkVersion=21 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=win_aarch64 --buildList=perf --customTarget="" --testTarget=sanity.perf --tapPath=C:/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests/\\TKG\\output_17510617532875\\ --tapName=Test_openjdk21_hs_sanity.perf_aarch64_windows.tap --comment="" [2025-06-27T22:13:32.946Z] [2025-06-27T22:13:32.946Z] [2025-06-27T22:13:32.946Z] TEST TARGETS SUMMARY [2025-06-27T22:13:32.946Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-27T22:13:32.946Z] DISABLED test targets: [2025-06-27T22:13:32.946Z] dacapo-lusearch-fix_0 [2025-06-27T22:13:32.946Z] renaissance-future-genetic_0 [2025-06-27T22:13:32.946Z] [2025-06-27T22:13:32.946Z] PASSED test targets: [2025-06-27T22:13:32.946Z] dacapo-h2_0 [2025-06-27T22:13:32.946Z] renaissance-akka-uct_0 [2025-06-27T22:13:32.946Z] renaissance-fj-kmeans_0 [2025-06-27T22:13:32.946Z] renaissance-scala-kmeans_0 [2025-06-27T22:13:32.946Z] [2025-06-27T22:13:32.946Z] FAILED test targets: [2025-06-27T22:13:32.946Z] renaissance-naive-bayes_0 [2025-06-27T22:13:32.946Z] [2025-06-27T22:13:32.946Z] TOTAL: 8 EXECUTED: 5 PASSED: 4 FAILED: 1 DISABLED: 2 SKIPPED: 1 [2025-06-27T22:13:32.946Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-27T22:13:32.946Z] [2025-06-27T22:13:32.946Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-27T22:13:32.946Z] make[1]: Leaving directory '/cygdrive/c/Users/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows/aqa-tests/TKG' [2025-06-27T22:13:32.946Z] make: *** [makefile:62: _sanity.perf] Error 2 [Pipeline] sh [2025-06-27T22:13:33.409Z] ++ uname [2025-06-27T22:13:33.715Z] + '[' CYGWIN_NT-10.0-22000 = AIX ']' [2025-06-27T22:13:33.715Z] ++ uname [2025-06-27T22:13:33.715Z] + '[' CYGWIN_NT-10.0-22000 = SunOS ']' [2025-06-27T22:13:33.715Z] ++ uname [2025-06-27T22:13:33.715Z] + '[' CYGWIN_NT-10.0-22000 = '*BSD' ']' [2025-06-27T22:13:33.715Z] + MAKE=make [2025-06-27T22:13:33.715Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-27T22:13:33.715Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-27T22:13:33.761Z] $ ssh-agent -k [2025-06-27T22:13:33.827Z] unset SSH_AUTH_SOCK; [2025-06-27T22:13:33.827Z] unset SSH_AGENT_PID; [2025-06-27T22:13:33.827Z] echo Agent pid 345 killed; [2025-06-27T22:13:33.892Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] writeJSON [Pipeline] archiveArtifacts [2025-06-27T22:13:34.021Z] Archiving artifacts [2025-06-27T22:13:34.062Z] Recording fingerprints [Pipeline] echo [2025-06-27T22:13:34.109Z] DaCapo-h2 metric found and archived [Pipeline] echo [2025-06-27T22:13:34.143Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-27T22:13:34.228Z] TAP Reports Processing: START [2025-06-27T22:13:34.229Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-27T22:13:34.363Z] Saving reports... [2025-06-27T22:13:34.383Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_sanity.perf_aarch64_windows/builds/126/tap-master-files/aqa-tests/TKG/output_17510617532875/Test_openjdk21_hs_sanity.perf_aarch64_windows.tap' [2025-06-27T22:13:34.383Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_sanity.perf_aarch64_windows/builds/126/tap-master-files/aqa-tests/TKG/output_17510617532875/Test_openjdk21_hs_sanity.perf_aarch64_windows.tap]. [2025-06-27T22:13:34.387Z] There are failed test cases. Marking build as UNSTABLE [2025-06-27T22:13:34.387Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-27T22:13:34.397Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T22:13:34.419Z] Archiving artifacts [2025-06-27T22:13:34.455Z] Recording fingerprints [Pipeline] echo [2025-06-27T22:13:34.499Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T22:13:34.531Z] Archiving artifacts [2025-06-27T22:13:34.664Z] Recording fingerprints [Pipeline] sh [2025-06-27T22:13:35.242Z] + tar -cf benchmark_test_output.tar.gz ./aqa-tests/TKG/output_17510617532875 [Pipeline] echo [2025-06-27T22:13:47.001Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-27T22:13:47.026Z] Archiving artifacts [2025-06-27T22:14:20.706Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-27T22:14:25.038Z] Tap file found: aqa-tests\TKG\output_17510617532875\Test_openjdk21_hs_sanity.perf_aarch64_windows.tap... [Pipeline] readFile [Pipeline] echo [2025-06-27T22:14:25.128Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=renaissance-naive-bayes_0&BASE_DOCKER_REGISTRY_CREDENTIAL_ID=&TEST_FLAG=&UPSTREAM_TEST_JOB_NAME=&DOCKER_REQUIRED=false&ACTIVE_NODE_TIMEOUT=5&VENDOR_TEST_DIRS=&EXTRA_DOCKER_ARGS=&TKG_OWNER_BRANCH=adoptium%3Amaster&OPENJ9_SYSTEMTEST_OWNER_BRANCH=eclipse%3Amaster&PLATFORM=aarch64_windows&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=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk21u%2Fjdk21u-windows-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%2B8_adopt&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=&TEST_TIME=120&JDK_IMPL=hotspot&SSH_AGENT_CREDENTIAL=&AUTO_DETECT=true&SLACK_CHANNEL=aqavit-bot&DYNAMIC_COMPILE=false&RELATED_NODES=&ADOPTOPENJDK_SYSTEMTEST_OWNER_BRANCH=adoptium%3Amaster&APPLICATION_OPTIONS=&CUSTOMIZED_SDK_URL_CREDENTIAL_ID=eclipse_temurin_bot_email_and_token&ARCHIVE_TEST_RESULTS=false&NUM_MACHINES=&OPENJDK_SHA=&TRSS_URL=&RERUN_FAILURE=false&USE_TESTENV_PROPERTIES=false&BUILD_LIST=perf&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=58&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-27T22:14:25.157Z] Recording test results [2025-06-27T22:14:27.756Z] None of the test reports contained any result [2025-06-27T22:14:27.757Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-27T22:14:27.782Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-27T22:14:28.229Z] + aqa-tests/terminateTestProcesses.sh null [2025-06-27T22:14:27.464Z] No test report files were found. Configuration error? [2025-06-27T22:14:28.525Z] Windows machine, using powershell queries... [2025-06-27T22:14:30.122Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-27T22:14:30.246Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T22:14:30.246Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T22:14:45.691Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-27T22:14:46.130Z] + find /cygdrive/c/temp -name '*core*' -print -exec rm -f '{}' ';' [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-27T22:14:46.502Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-27T22:14:46.638Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-27T22:14:46.687Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-27T22:14:46.779Z] Running on test-docker-ubuntu2404-armv8-3 in /home/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows [Pipeline] { [Pipeline] cleanWs [2025-06-27T22:14:47.073Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T22:14:47.074Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T22:14:47.235Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-27T22:14:47.656Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T22:14:47.656Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T22:14:47.790Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-27T22:14:47.874Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-27T22:14:47.912Z] Running on test-docker-centosstream9-armv8-1 in /home/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows [Pipeline] { [Pipeline] echo [2025-06-27T22:14:47.938Z] Generating rerun Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun) [Pipeline] echo [2025-06-27T22:14:47.980Z] GENERATE_JOBS is set to true, set test job Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-06-27T22:14:49.738Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-27T22:14:50.836Z] Processing DSL script testJobTemplate [2025-06-27T22:18:24.157Z] LEVELS: [sanity] [2025-06-27T22:18:24.157Z] JDK_VERSIONS: [8] [2025-06-27T22:18:24.157Z] GROUPS: [perf] [2025-06-27T22:18:24.157Z] ARCH_OS_LIST: [aarch64_windows] [2025-06-27T22:18:24.275Z] Added items: [2025-06-27T22:18:24.275Z] GeneratedJob{name='Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-27T22:18:25.462Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun) [Pipeline] build [2025-06-27T22:18:25.490Z] Scheduling project: Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun [2025-06-27T22:18:31.037Z] Starting building: Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun #1 [2025-06-28T17:28:51.913Z] Build Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun #1 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-28T17:28:52.040Z] Running on test-docker-ubuntu1804-armv8l-4 in /home/jenkins/workspace/Test_openjdk21_hs_sanity.perf_aarch64_windows [Pipeline] { [Pipeline] cleanWs [2025-06-28T17:28:52.330Z] [WS-CLEANUP] Deleting project workspace... [2025-06-28T17:28:52.330Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-28T17:28:52.464Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-28T17:28:52.475Z] Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun #1 completed with status UNSTABLE [Pipeline] timeout [2025-06-28T17:28:52.477Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-28T17:28:53.424Z] Copied 1 artifact from "Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun" build number 1 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-28T17:28:53.608Z] TAP Reports Processing: START [2025-06-28T17:28:53.609Z] Looking for TAP results report in workspace using pattern: Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun/1/**/*.tap [2025-06-28T17:28:53.743Z] Saving reports... [2025-06-28T17:28:53.879Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_sanity.perf_aarch64_windows/builds/126/tap-master-files/Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun/1/aqa-tests/TKG/output_17511316485605/Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun.tap' [2025-06-28T17:28:53.879Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_sanity.perf_aarch64_windows/builds/126/tap-master-files/Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun/1/aqa-tests/TKG/output_17511316485605/Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun.tap]. [2025-06-28T17:28:53.882Z] There are failed test cases. Marking build as UNSTABLE [2025-06-28T17:28:53.900Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-28T17:28:53.907Z] Saving Test_openjdk21_hs_sanity.perf_aarch64_windows_rerun/1/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-28T17:28:54.044Z] Archiving artifacts [2025-06-28T17:28:54.313Z] Recording fingerprints [Pipeline] findFiles [Pipeline] readFile Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. [Pipeline] cleanWs [2025-06-28T17:28:55.473Z] [WS-CLEANUP] Deleting project workspace... [2025-06-28T17:28:55.473Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-28T17:28:55.604Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE