[2025-07-01T20:16:10.804Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests/perf/renaissance' [2025-07-01T20:16:10.804Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests/perf' [2025-07-01T20:16:10.804Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests' [2025-07-01T20:16:10.804Z] [2025-07-01T20:16:10.804Z] [2025-07-01T20:16:10.804Z] All tests finished, run result summary: [2025-07-01T20:16:10.804Z] cd "/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-07-01T20:16:10.804Z] perl "resultsSum.pl" --failuremk="/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests/TKG/../TKG/failedtargets.mk" --resultFile="/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests/TKG/../TKG/output_17513923674795/TestTargetResult" --platFile="/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests/TKG/../TKG/resources/buildPlatformMap.properties" --diagnostic=failure --jdkVersion=21 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=linux_390-64 --buildList=perf --customTarget="" --testTarget=extended.perf --tapPath=/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests/TKG/../TKG/output_17513923674795/ --tapName=Test_openjdk21_hs_extended.perf_s390x_linux.tap --comment="" [2025-07-01T20:16:10.804Z] [2025-07-01T20:16:10.804Z] [2025-07-01T20:16:10.804Z] TEST TARGETS SUMMARY [2025-07-01T20:16:10.804Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-07-01T20:16:10.804Z] DISABLED test targets: [2025-07-01T20:16:10.804Z] dacapo-avrora_0 [2025-07-01T20:16:10.804Z] dacapo-tomcat_0 [2025-07-01T20:16:10.804Z] renaissance-finagle-chirper_0 [2025-07-01T20:16:10.804Z] [2025-07-01T20:16:10.804Z] PASSED test targets: [2025-07-01T20:16:10.804Z] dacapo-jython_0 [2025-07-01T20:16:10.804Z] dacapo-luindex_0 [2025-07-01T20:16:10.804Z] dacapo-pmd_0 [2025-07-01T20:16:10.804Z] dacapo-sunflow_0 [2025-07-01T20:16:10.804Z] dacapo-xalan_0 [2025-07-01T20:16:10.804Z] renaissance-als_0 [2025-07-01T20:16:10.804Z] renaissance-chi-square_0 [2025-07-01T20:16:10.804Z] renaissance-db-shootout_0 [2025-07-01T20:16:10.804Z] renaissance-dec-tree_0 [2025-07-01T20:16:10.804Z] renaissance-finagle-http_0 [2025-07-01T20:16:10.804Z] renaissance-gauss-mix_0 [2025-07-01T20:16:10.804Z] renaissance-log-regression_0 [2025-07-01T20:16:10.804Z] renaissance-mnemonics_0 [2025-07-01T20:16:10.804Z] renaissance-movie-lens_0 [2025-07-01T20:16:10.804Z] renaissance-par-mnemonics_0 [2025-07-01T20:16:10.804Z] renaissance-philosophers_0 [2025-07-01T20:16:10.804Z] [2025-07-01T20:16:10.804Z] FAILED test targets: [2025-07-01T20:16:10.804Z] dacapo-fop_0 [2025-07-01T20:16:10.804Z] [2025-07-01T20:16:10.804Z] TOTAL: 20 EXECUTED: 17 PASSED: 16 FAILED: 1 DISABLED: 3 SKIPPED: 0 [2025-07-01T20:16:10.804Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-07-01T20:16:10.804Z] [2025-07-01T20:16:10.804Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-07-01T20:16:10.804Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux/aqa-tests/TKG' [2025-07-01T20:16:10.804Z] make: *** [makefile:62: _extended.perf] Error 2 [Pipeline] sh [2025-07-01T20:16:12.361Z] ++ uname [2025-07-01T20:16:12.361Z] + '[' Linux = AIX ']' [2025-07-01T20:16:12.361Z] ++ uname [2025-07-01T20:16:12.361Z] + '[' Linux = SunOS ']' [2025-07-01T20:16:12.361Z] ++ uname [2025-07-01T20:16:12.361Z] + '[' Linux = '*BSD' ']' [2025-07-01T20:16:12.361Z] + MAKE=make [2025-07-01T20:16:12.361Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-07-01T20:16:12.361Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-07-01T20:16:12.684Z] $ ssh-agent -k [2025-07-01T20:16:12.695Z] unset SSH_AUTH_SOCK; [2025-07-01T20:16:12.695Z] unset SSH_AGENT_PID; [2025-07-01T20:16:12.695Z] echo Agent pid 8552 killed; [2025-07-01T20:16:13.186Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] } [2025-07-01T20:16:13.214Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-07-01T20:16:13.847Z] no DaCapo-h2 metric found [Pipeline] echo [2025-07-01T20:16:13.889Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-07-01T20:16:14.077Z] TAP Reports Processing: START [2025-07-01T20:16:14.078Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-07-01T20:16:14.300Z] Saving reports... [2025-07-01T20:16:14.390Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_extended.perf_s390x_linux/builds/102/tap-master-files/aqa-tests/TKG/output_17513923674795/Test_openjdk21_hs_extended.perf_s390x_linux.tap' [2025-07-01T20:16:14.390Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_extended.perf_s390x_linux/builds/102/tap-master-files/aqa-tests/TKG/output_17513923674795/Test_openjdk21_hs_extended.perf_s390x_linux.tap]. [2025-07-01T20:16:14.396Z] There are failed test cases. Marking build as UNSTABLE [2025-07-01T20:16:14.396Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-07-01T20:16:14.406Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-07-01T20:16:14.502Z] Archiving artifacts [2025-07-01T20:16:14.725Z] Recording fingerprints [Pipeline] echo [2025-07-01T20:16:14.839Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-07-01T20:16:14.934Z] Archiving artifacts [2025-07-01T20:16:15.325Z] Recording fingerprints [Pipeline] sh [2025-07-01T20:16:16.583Z] + tar -cf benchmark_test_output.tar.gz ./aqa-tests/TKG/output_17513923674795 [Pipeline] echo [2025-07-01T20:16:16.860Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-07-01T20:16:16.956Z] Archiving artifacts [2025-07-01T20:16:17.136Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-07-01T20:16:19.678Z] Tap file found: aqa-tests/TKG/output_17513923674795/Test_openjdk21_hs_extended.perf_s390x_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-07-01T20:16:19.944Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=dacapo-fop_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=s390x_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=&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-linux-s390x-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=133&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-07-01T20:16:20.053Z] Recording test results [2025-07-01T20:16:20.508Z] None of the test reports contained any result [2025-07-01T20:16:20.509Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-07-01T20:16:20.551Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-07-01T20:16:20.440Z] No test report files were found. Configuration error? [2025-07-01T20:16:21.736Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-07-01T20:16:21.736Z] Unix type machine.. [2025-07-01T20:16:21.736Z] Running on a Linux host [2025-07-01T20:16:21.736Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-07-01T20:16:22.217Z] [WS-CLEANUP] Deleting project workspace... [2025-07-01T20:16:22.217Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-01T20:16:23.629Z] [WS-CLEANUP] done [Pipeline] sh [2025-07-01T20:16:24.787Z] + find /tmp -name '*core*' -print -exec rm -f '{}' ';' [2025-07-01T20:16:29.774Z] + true [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-07-01T20:16:29.823Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-07-01T20:16:30.000Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-07-01T20:16:30.044Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-07-01T20:16:30.161Z] Running on test-osuosl-ubuntu2404-ppc64le-2 in /home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux [Pipeline] { [Pipeline] cleanWs [2025-07-01T20:16:30.555Z] [WS-CLEANUP] Deleting project workspace... [2025-07-01T20:16:30.555Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-01T20:16:30.734Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-07-01T20:16:31.287Z] [WS-CLEANUP] Deleting project workspace... [2025-07-01T20:16:31.288Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-01T20:16:31.464Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-07-01T20:16:31.575Z] allocate a node for generating rerun job ... [Pipeline] node [2025-07-01T20:16:31.618Z] Running on test-docker-ubuntu2404-armv7-7 in /home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux [Pipeline] { [Pipeline] echo [2025-07-01T20:16:31.642Z] Generating rerun Test_openjdk21_hs_extended.perf_s390x_linux_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk21_hs_extended.perf_s390x_linux_rerun) [Pipeline] echo [2025-07-01T20:16:31.689Z] GENERATE_JOBS is set to true, set test job Test_openjdk21_hs_extended.perf_s390x_linux_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-07-01T20:16:33.423Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-07-01T20:16:34.547Z] Processing DSL script testJobTemplate [2025-07-01T20:20:04.810Z] LEVELS: [extended] [2025-07-01T20:20:04.810Z] JDK_VERSIONS: [8] [2025-07-01T20:20:04.810Z] GROUPS: [perf] [2025-07-01T20:20:04.810Z] ARCH_OS_LIST: [s390x_linux] [2025-07-01T20:20:05.040Z] Added items: [2025-07-01T20:20:05.040Z] GeneratedJob{name='Test_openjdk21_hs_extended.perf_s390x_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-07-01T20:20:05.307Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk21_hs_extended.perf_s390x_linux_rerun) [Pipeline] build [2025-07-01T20:20:05.333Z] Scheduling project: Test_openjdk21_hs_extended.perf_s390x_linux_rerun [2025-07-01T20:20:14.004Z] Starting building: Test_openjdk21_hs_extended.perf_s390x_linux_rerun #5 [2025-07-01T20:25:59.807Z] Build Test_openjdk21_hs_extended.perf_s390x_linux_rerun #5 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-07-01T20:25:59.911Z] Running on test-docker-ubuntu2404-armv8-1 in /home/jenkins/workspace/Test_openjdk21_hs_extended.perf_s390x_linux [Pipeline] { [Pipeline] cleanWs [2025-07-01T20:26:00.192Z] [WS-CLEANUP] Deleting project workspace... [2025-07-01T20:26:00.192Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-01T20:26:00.326Z] [WS-CLEANUP] done [Pipeline] echo [2025-07-01T20:26:00.333Z] Test_openjdk21_hs_extended.perf_s390x_linux_rerun #5 completed with status UNSTABLE [Pipeline] timeout [2025-07-01T20:26:00.335Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-07-01T20:26:01.269Z] Copied 1 artifact from "Test_openjdk21_hs_extended.perf_s390x_linux_rerun" build number 5 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-07-01T20:26:01.454Z] TAP Reports Processing: START [2025-07-01T20:26:01.455Z] Looking for TAP results report in workspace using pattern: Test_openjdk21_hs_extended.perf_s390x_linux_rerun/5/**/*.tap [2025-07-01T20:26:01.584Z] Saving reports... [2025-07-01T20:26:01.840Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_extended.perf_s390x_linux/builds/102/tap-master-files/Test_openjdk21_hs_extended.perf_s390x_linux_rerun/5/aqa-tests/TKG/output_17514015382261/Test_openjdk21_hs_extended.perf_s390x_linux_rerun.tap' [2025-07-01T20:26:01.840Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_extended.perf_s390x_linux/builds/102/tap-master-files/Test_openjdk21_hs_extended.perf_s390x_linux_rerun/5/aqa-tests/TKG/output_17514015382261/Test_openjdk21_hs_extended.perf_s390x_linux_rerun.tap]. [2025-07-01T20:26:01.842Z] There are failed test cases. Marking build as UNSTABLE [2025-07-01T20:26:01.853Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-07-01T20:26:01.862Z] Saving Test_openjdk21_hs_extended.perf_s390x_linux_rerun/5/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-07-01T20:26:01.998Z] Archiving artifacts [2025-07-01T20:26:02.265Z] 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. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? 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-07-01T20:26:03.461Z] [WS-CLEANUP] Deleting project workspace... [2025-07-01T20:26:03.461Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-01T20:26:03.594Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE