[2025-06-26T21:06:53.746Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/perf/renaissance' [2025-06-26T21:06:53.746Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/perf' [2025-06-26T21:06:53.746Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests' [2025-06-26T21:06:53.746Z] [2025-06-26T21:06:53.746Z] [2025-06-26T21:06:53.746Z] All tests finished, run result summary: [2025-06-26T21:06:53.746Z] cd "/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-06-26T21:06:53.746Z] 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_17509718557293/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_17509718557293/ --tapName=Test_openjdk8_hs_extended.perf_arm_linux.tap --comment="" [2025-06-26T21:06:54.274Z] [2025-06-26T21:06:54.274Z] [2025-06-26T21:06:54.274Z] TEST TARGETS SUMMARY [2025-06-26T21:06:54.274Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-26T21:06:54.274Z] DISABLED test targets: [2025-06-26T21:06:54.274Z] dacapo-luindex_0 [2025-06-26T21:06:54.274Z] dacapo-tomcat_0 [2025-06-26T21:06:54.274Z] renaissance-als_0 [2025-06-26T21:06:54.274Z] renaissance-chi-square_0 [2025-06-26T21:06:54.274Z] renaissance-dec-tree_0 [2025-06-26T21:06:54.274Z] renaissance-finagle-chirper_0 [2025-06-26T21:06:54.274Z] renaissance-gauss-mix_0 [2025-06-26T21:06:54.274Z] renaissance-log-regression_0 [2025-06-26T21:06:54.274Z] renaissance-movie-lens_0 [2025-06-26T21:06:54.274Z] [2025-06-26T21:06:54.274Z] PASSED test targets: [2025-06-26T21:06:54.274Z] dacapo-avrora_0 [2025-06-26T21:06:54.274Z] dacapo-fop_0 [2025-06-26T21:06:54.274Z] dacapo-jython_0 [2025-06-26T21:06:54.274Z] dacapo-pmd_0 [2025-06-26T21:06:54.274Z] dacapo-sunflow_0 [2025-06-26T21:06:54.274Z] renaissance-db-shootout_0 [2025-06-26T21:06:54.274Z] renaissance-finagle-http_0 [2025-06-26T21:06:54.274Z] renaissance-mnemonics_0 [2025-06-26T21:06:54.274Z] renaissance-par-mnemonics_0 [2025-06-26T21:06:54.274Z] renaissance-philosophers_0 [2025-06-26T21:06:54.274Z] [2025-06-26T21:06:54.274Z] FAILED test targets: [2025-06-26T21:06:54.274Z] dacapo-xalan_0 [2025-06-26T21:06:54.274Z] [2025-06-26T21:06:54.274Z] TOTAL: 20 EXECUTED: 11 PASSED: 10 FAILED: 1 DISABLED: 9 SKIPPED: 0 [2025-06-26T21:06:54.274Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-26T21:06:54.274Z] [2025-06-26T21:06:54.274Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-26T21:06:54.274Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG' [2025-06-26T21:06:54.274Z] make: *** [makefile:62: _extended.perf] Error 2 [Pipeline] sh [2025-06-26T21:06:56.756Z] + uname [2025-06-26T21:06:56.756Z] + [ Linux = AIX ] [2025-06-26T21:06:56.756Z] + uname [2025-06-26T21:06:56.756Z] + [ Linux = SunOS ] [2025-06-26T21:06:56.756Z] + uname [2025-06-26T21:06:56.756Z] + [ Linux = *BSD ] [2025-06-26T21:06:56.756Z] + MAKE=make [2025-06-26T21:06:56.756Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-26T21:06:56.756Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-26T21:06:57.373Z] $ ssh-agent -k [2025-06-26T21:06:57.382Z] unset SSH_AUTH_SOCK; [2025-06-26T21:06:57.383Z] unset SSH_AGENT_PID; [2025-06-26T21:06:57.383Z] echo Agent pid 2757 killed; [2025-06-26T21:06:58.184Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] } [2025-06-26T21:06:58.213Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-06-26T21:06:59.038Z] no DaCapo-h2 metric found [Pipeline] echo [2025-06-26T21:06:59.076Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-26T21:06:59.327Z] TAP Reports Processing: START [2025-06-26T21:06:59.328Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-26T21:06:59.575Z] Saving reports... [2025-06-26T21:06:59.759Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/170/tap-master-files/aqa-tests/TKG/output_17509718557293/Test_openjdk8_hs_extended.perf_arm_linux.tap' [2025-06-26T21:06:59.759Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/170/tap-master-files/aqa-tests/TKG/output_17509718557293/Test_openjdk8_hs_extended.perf_arm_linux.tap]. [2025-06-26T21:06:59.762Z] There are failed test cases. Marking build as UNSTABLE [2025-06-26T21:06:59.762Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-26T21:06:59.769Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T21:06:59.952Z] Archiving artifacts [2025-06-26T21:07:02.934Z] Recording fingerprints [Pipeline] echo [2025-06-26T21:07:03.364Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T21:07:03.601Z] Archiving artifacts [2025-06-26T21:07:04.008Z] Recording fingerprints [Pipeline] sh [2025-06-26T21:07:06.169Z] + tar -cf benchmark_test_output.tar.gz ./aqa-tests/TKG/output_17509718557293 [Pipeline] echo [2025-06-26T21:07:06.700Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-26T21:07:06.900Z] Archiving artifacts [2025-06-26T21:07:09.125Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-26T21:07:11.359Z] Tap file found: aqa-tests/TKG/output_17509718557293/Test_openjdk8_hs_extended.perf_arm_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-06-26T21:07:11.661Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=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=485&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-26T21:07:11.861Z] Recording test results [2025-06-26T21:07:15.423Z] No test report files were found. Configuration error? [2025-06-26T21:07:20.697Z] None of the test reports contained any result [2025-06-26T21:07:20.697Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T21:07:20.730Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-26T21:07:22.634Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-06-26T21:07:22.634Z] Unix type machine.. [2025-06-26T21:07:22.634Z] Running on a Linux host [2025-06-26T21:07:22.634Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-26T21:07:23.539Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T21:07:23.539Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T21:07:28.089Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-26T21:07:30.134Z] + find /tmp -name *core* -print -exec rm -f {} ; [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-26T21:07:30.699Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T21:07:30.844Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-26T21:07:30.872Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-26T21:07:30.967Z] Running on test-docker-ubuntu2404-armv8-1 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] cleanWs [2025-06-26T21:07:31.274Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T21:07:31.274Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T21:07:31.414Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-26T21:07:31.849Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T21:07:31.850Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T21:07:31.989Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-26T21:07:32.099Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-26T21:07:32.126Z] Running on test-docker-centosstream9-armv8-1 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] echo [2025-06-26T21:07:32.141Z] 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-06-26T21:07:32.177Z] 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-06-26T21:07:35.083Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-26T21:07:36.520Z] Processing DSL script testJobTemplate [2025-06-26T21:11:58.544Z] LEVELS: [extended] [2025-06-26T21:11:58.544Z] JDK_VERSIONS: [8] [2025-06-26T21:11:58.544Z] GROUPS: [perf] [2025-06-26T21:11:58.544Z] ARCH_OS_LIST: [arm_linux] [2025-06-26T21:11:58.670Z] Existing items: [2025-06-26T21:11:58.670Z] GeneratedJob{name='Test_openjdk8_hs_extended.perf_arm_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-26T21:11:58.966Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk8_hs_extended.perf_arm_linux_rerun) [Pipeline] build [2025-06-26T21:11:58.986Z] Scheduling project: Test_openjdk8_hs_extended.perf_arm_linux_rerun [2025-06-26T21:12:06.117Z] Starting building: Test_openjdk8_hs_extended.perf_arm_linux_rerun #5 [2025-06-26T21:21:28.375Z] Build Test_openjdk8_hs_extended.perf_arm_linux_rerun #5 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-26T21:21:28.504Z] Running on test-rise-ubuntu2404-riscv64-2 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] cleanWs [2025-06-26T21:21:28.664Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T21:21:28.664Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T21:21:28.724Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-26T21:21:28.735Z] Test_openjdk8_hs_extended.perf_arm_linux_rerun #5 completed with status UNSTABLE [Pipeline] timeout [2025-06-26T21:21:28.738Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-26T21:21:29.022Z] Copied 1 artifact from "Test_openjdk8_hs_extended.perf_arm_linux_rerun" build number 5 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-26T21:21:29.132Z] TAP Reports Processing: START [2025-06-26T21:21:29.133Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_extended.perf_arm_linux_rerun/5/**/*.tap [2025-06-26T21:21:29.165Z] Saving reports... [2025-06-26T21:21:29.228Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/170/tap-master-files/Test_openjdk8_hs_extended.perf_arm_linux_rerun/5/aqa-tests/TKG/output_17509728483326/Test_openjdk8_hs_extended.perf_arm_linux_rerun.tap' [2025-06-26T21:21:29.228Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/170/tap-master-files/Test_openjdk8_hs_extended.perf_arm_linux_rerun/5/aqa-tests/TKG/output_17509728483326/Test_openjdk8_hs_extended.perf_arm_linux_rerun.tap]. [2025-06-26T21:21:29.231Z] There are failed test cases. Marking build as UNSTABLE [2025-06-26T21:21:29.248Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-26T21:21:29.259Z] Saving Test_openjdk8_hs_extended.perf_arm_linux_rerun/5/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T21:21:29.293Z] Archiving artifacts [2025-06-26T21:21:29.371Z] 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. Did you forget the `def` keyword? 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-26T21:21:29.753Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T21:21:29.753Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T21:21:29.835Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE