[2025-07-03T21:02:11.801Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/perf/renaissance' [2025-07-03T21:02:11.801Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/perf' [2025-07-03T21:02:11.801Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests' [2025-07-03T21:02:11.801Z] [2025-07-03T21:02:11.801Z] [2025-07-03T21:02:11.801Z] All tests finished, run result summary: [2025-07-03T21:02:11.801Z] cd "/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-07-03T21:02:11.801Z] perl "resultsSum.pl" --failuremk="/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG/../TKG/failedtargets.mk" --resultFile="/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG/../TKG/output_17515763987322/TestTargetResult" --platFile="/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG/../TKG/resources/buildPlatformMap.properties" --diagnostic=failure --jdkVersion=8 --jdkImpl=hotspot --jdkVendor="temurin" --spec=linux_arm --buildList=perf --customTarget="" --testTarget=extended.perf --tapPath=/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG/../TKG/output_17515763987322/ --tapName=Test_openjdk8_hs_extended.perf_arm_linux.tap --comment="" [2025-07-03T21:02:11.801Z] [2025-07-03T21:02:11.801Z] [2025-07-03T21:02:11.801Z] TEST TARGETS SUMMARY [2025-07-03T21:02:11.801Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-07-03T21:02:11.801Z] DISABLED test targets: [2025-07-03T21:02:11.801Z] dacapo-luindex_0 [2025-07-03T21:02:11.801Z] dacapo-tomcat_0 [2025-07-03T21:02:11.801Z] renaissance-als_0 [2025-07-03T21:02:11.801Z] renaissance-chi-square_0 [2025-07-03T21:02:11.801Z] renaissance-dec-tree_0 [2025-07-03T21:02:11.801Z] renaissance-finagle-chirper_0 [2025-07-03T21:02:11.801Z] renaissance-gauss-mix_0 [2025-07-03T21:02:11.801Z] renaissance-log-regression_0 [2025-07-03T21:02:11.801Z] renaissance-movie-lens_0 [2025-07-03T21:02:11.801Z] [2025-07-03T21:02:11.801Z] PASSED test targets: [2025-07-03T21:02:11.801Z] dacapo-avrora_0 [2025-07-03T21:02:11.801Z] dacapo-fop_0 [2025-07-03T21:02:11.801Z] dacapo-jython_0 [2025-07-03T21:02:11.801Z] dacapo-sunflow_0 [2025-07-03T21:02:11.801Z] renaissance-db-shootout_0 [2025-07-03T21:02:11.801Z] renaissance-finagle-http_0 [2025-07-03T21:02:11.801Z] renaissance-mnemonics_0 [2025-07-03T21:02:11.801Z] renaissance-par-mnemonics_0 [2025-07-03T21:02:11.801Z] renaissance-philosophers_0 [2025-07-03T21:02:11.801Z] [2025-07-03T21:02:11.801Z] FAILED test targets: [2025-07-03T21:02:11.801Z] dacapo-pmd_0 [2025-07-03T21:02:11.801Z] dacapo-xalan_0 [2025-07-03T21:02:11.801Z] [2025-07-03T21:02:11.801Z] TOTAL: 20 EXECUTED: 11 PASSED: 9 FAILED: 2 DISABLED: 9 SKIPPED: 0 [2025-07-03T21:02:11.801Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-07-03T21:02:11.801Z] [2025-07-03T21:02:11.801Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-07-03T21:02:11.801Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG' [2025-07-03T21:02:11.801Z] make: *** [makefile:62: _extended.perf] Error 2 [Pipeline] sh [2025-07-03T21:02:13.803Z] + uname [2025-07-03T21:02:13.803Z] + [ Linux = AIX ] [2025-07-03T21:02:13.803Z] + uname [2025-07-03T21:02:13.803Z] + [ Linux = SunOS ] [2025-07-03T21:02:13.803Z] + uname [2025-07-03T21:02:13.803Z] + [ Linux = *BSD ] [2025-07-03T21:02:13.803Z] + MAKE=make [2025-07-03T21:02:13.803Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-07-03T21:02:13.803Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-07-03T21:02:14.249Z] $ ssh-agent -k [2025-07-03T21:02:14.260Z] unset SSH_AUTH_SOCK; [2025-07-03T21:02:14.260Z] unset SSH_AGENT_PID; [2025-07-03T21:02:14.260Z] echo Agent pid 1901176 killed; [2025-07-03T21:02:14.833Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] } [2025-07-03T21:02:14.865Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-07-03T21:02:15.310Z] no DaCapo-h2 metric found [Pipeline] echo [2025-07-03T21:02:15.355Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-07-03T21:02:15.575Z] TAP Reports Processing: START [2025-07-03T21:02:15.576Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-07-03T21:02:15.728Z] Saving reports... [2025-07-03T21:02:15.864Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/171/tap-master-files/aqa-tests/TKG/output_17515763987322/Test_openjdk8_hs_extended.perf_arm_linux.tap' [2025-07-03T21:02:15.864Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/171/tap-master-files/aqa-tests/TKG/output_17515763987322/Test_openjdk8_hs_extended.perf_arm_linux.tap]. [2025-07-03T21:02:15.869Z] There are failed test cases. Marking build as UNSTABLE [2025-07-03T21:02:15.869Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-07-03T21:02:15.879Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-07-03T21:02:16.016Z] Archiving artifacts [2025-07-03T21:02:16.275Z] Recording fingerprints [Pipeline] echo [2025-07-03T21:02:16.440Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-07-03T21:02:16.573Z] Archiving artifacts [2025-07-03T21:02:16.856Z] Recording fingerprints [Pipeline] sh [2025-07-03T21:02:18.676Z] + tar -cf benchmark_test_output.tar.gz ./aqa-tests/TKG/output_17515763987322 [Pipeline] echo [2025-07-03T21:02:19.059Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-07-03T21:02:19.194Z] Archiving artifacts [2025-07-03T21:02:25.832Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-07-03T21:02:27.890Z] Tap file found: aqa-tests/TKG/output_17515763987322/Test_openjdk8_hs_extended.perf_arm_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-07-03T21:02:28.123Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=dacapo-pmd_0,dacapo-xalan_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=arm_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=8&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faarch32-jdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-linux-arm-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=&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=486&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-07-03T21:02:28.264Z] Recording test results [2025-07-03T21:02:29.220Z] None of the test reports contained any result [2025-07-03T21:02:29.221Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-07-03T21:02:29.260Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-07-03T21:02:29.107Z] No test report files were found. Configuration error? [2025-07-03T21:02:30.684Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-07-03T21:02:30.684Z] Unix type machine.. [2025-07-03T21:02:30.684Z] Running on a Linux host [2025-07-03T21:02:30.684Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-07-03T21:02:31.338Z] [WS-CLEANUP] Deleting project workspace... [2025-07-03T21:02:31.339Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-03T21:02:34.877Z] [WS-CLEANUP] done [Pipeline] sh [2025-07-03T21:02:36.431Z] + find /tmp -name *core* -print -exec rm -f {} ; [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-07-03T21:02:36.854Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-07-03T21:02:37.020Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-07-03T21:02:37.064Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-07-03T21:02:37.119Z] Running on test-docker-amazon2023-armv8l-1 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] cleanWs [2025-07-03T21:02:37.409Z] [WS-CLEANUP] Deleting project workspace... [2025-07-03T21:02:37.409Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-03T21:02:37.548Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-07-03T21:02:37.963Z] [WS-CLEANUP] Deleting project workspace... [2025-07-03T21:02:37.963Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-03T21:02:38.092Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-07-03T21:02:38.220Z] allocate a node for generating rerun job ... [Pipeline] node [2025-07-03T21:02:38.302Z] Running on test-marist-rhel7-s390x-2 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] echo [2025-07-03T21:02:38.321Z] Generating rerun Test_openjdk8_hs_extended.perf_arm_linux_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk8_hs_extended.perf_arm_linux_rerun) [Pipeline] echo [2025-07-03T21:02:38.364Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_extended.perf_arm_linux_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-07-03T21:02:39.717Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-07-03T21:02:40.517Z] Processing DSL script testJobTemplate [2025-07-03T21:05:38.667Z] LEVELS: [extended] [2025-07-03T21:05:38.667Z] JDK_VERSIONS: [8] [2025-07-03T21:05:38.667Z] GROUPS: [perf] [2025-07-03T21:05:38.667Z] ARCH_OS_LIST: [arm_linux] [2025-07-03T21:05:38.777Z] Existing items: [2025-07-03T21:05:38.777Z] GeneratedJob{name='Test_openjdk8_hs_extended.perf_arm_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-07-03T21:05:39.083Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk8_hs_extended.perf_arm_linux_rerun) [Pipeline] build [2025-07-03T21:05:39.099Z] Scheduling project: Test_openjdk8_hs_extended.perf_arm_linux_rerun [2025-07-03T21:05:45.678Z] Starting building: Test_openjdk8_hs_extended.perf_arm_linux_rerun #6 [2025-07-03T21:32:38.319Z] Build Test_openjdk8_hs_extended.perf_arm_linux_rerun #6 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-07-03T21:32:38.422Z] Running on test-docker-sles15-s390x-1 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] cleanWs [2025-07-03T21:32:38.635Z] [WS-CLEANUP] Deleting project workspace... [2025-07-03T21:32:38.635Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-03T21:32:38.723Z] [WS-CLEANUP] done [Pipeline] echo [2025-07-03T21:32:38.732Z] Test_openjdk8_hs_extended.perf_arm_linux_rerun #6 completed with status UNSTABLE [Pipeline] timeout [2025-07-03T21:32:38.735Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-07-03T21:32:39.475Z] Copied 1 artifact from "Test_openjdk8_hs_extended.perf_arm_linux_rerun" build number 6 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-07-03T21:32:39.625Z] TAP Reports Processing: START [2025-07-03T21:32:39.626Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_extended.perf_arm_linux_rerun/6/**/*.tap [2025-07-03T21:32:39.724Z] Saving reports... [2025-07-03T21:32:39.898Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/171/tap-master-files/Test_openjdk8_hs_extended.perf_arm_linux_rerun/6/aqa-tests/TKG/output_17515782905034/Test_openjdk8_hs_extended.perf_arm_linux_rerun.tap' [2025-07-03T21:32:39.898Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/171/tap-master-files/Test_openjdk8_hs_extended.perf_arm_linux_rerun/6/aqa-tests/TKG/output_17515782905034/Test_openjdk8_hs_extended.perf_arm_linux_rerun.tap]. [2025-07-03T21:32:39.901Z] There are failed test cases. Marking build as UNSTABLE [2025-07-03T21:32:39.919Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-07-03T21:32:39.931Z] Saving Test_openjdk8_hs_extended.perf_arm_linux_rerun/6/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-07-03T21:32:40.025Z] Archiving artifacts [2025-07-03T21:32:40.248Z] 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. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? 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-03T21:32:41.135Z] [WS-CLEANUP] Deleting project workspace... [2025-07-03T21:32:41.135Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-07-03T21:32:41.227Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE