[2025-05-31T20:59:51.956Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/perf/renaissance' [2025-05-31T20:59:51.956Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/perf' [2025-05-31T20:59:51.956Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests' [2025-05-31T20:59:51.956Z] [2025-05-31T20:59:51.956Z] [2025-05-31T20:59:51.956Z] All tests finished, run result summary: [2025-05-31T20:59:51.956Z] cd "/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-05-31T20:59:51.956Z] 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_17487251369377/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_17487251369377/ --tapName=Test_openjdk8_hs_extended.perf_arm_linux.tap --comment="" [2025-05-31T20:59:51.956Z] [2025-05-31T20:59:51.956Z] [2025-05-31T20:59:51.956Z] TEST TARGETS SUMMARY [2025-05-31T20:59:51.956Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-05-31T20:59:51.956Z] DISABLED test targets: [2025-05-31T20:59:51.956Z] dacapo-tomcat_0 [2025-05-31T20:59:51.956Z] renaissance-als_0 [2025-05-31T20:59:51.956Z] renaissance-chi-square_0 [2025-05-31T20:59:51.956Z] renaissance-db-shootout_0 [2025-05-31T20:59:51.956Z] renaissance-dec-tree_0 [2025-05-31T20:59:51.956Z] renaissance-finagle-chirper_0 [2025-05-31T20:59:51.956Z] renaissance-gauss-mix_0 [2025-05-31T20:59:51.956Z] renaissance-log-regression_0 [2025-05-31T20:59:51.956Z] renaissance-movie-lens_0 [2025-05-31T20:59:51.956Z] [2025-05-31T20:59:51.956Z] PASSED test targets: [2025-05-31T20:59:51.956Z] dacapo-avrora_0 [2025-05-31T20:59:51.956Z] dacapo-fop_0 [2025-05-31T20:59:51.956Z] dacapo-jython_0 [2025-05-31T20:59:51.956Z] dacapo-luindex_0 [2025-05-31T20:59:51.956Z] dacapo-pmd_0 [2025-05-31T20:59:51.956Z] dacapo-sunflow_0 [2025-05-31T20:59:51.956Z] renaissance-finagle-http_0 [2025-05-31T20:59:51.956Z] renaissance-mnemonics_0 [2025-05-31T20:59:51.956Z] renaissance-par-mnemonics_0 [2025-05-31T20:59:51.956Z] renaissance-philosophers_0 [2025-05-31T20:59:51.956Z] [2025-05-31T20:59:51.956Z] FAILED test targets: [2025-05-31T20:59:51.956Z] dacapo-xalan_0 [2025-05-31T20:59:51.956Z] [2025-05-31T20:59:51.956Z] TOTAL: 20 EXECUTED: 11 PASSED: 10 FAILED: 1 DISABLED: 9 SKIPPED: 0 [2025-05-31T20:59:51.956Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-05-31T20:59:51.956Z] [2025-05-31T20:59:51.956Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-05-31T20:59:51.956Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux/aqa-tests/TKG' [2025-05-31T20:59:51.956Z] make: *** [makefile:62: _extended.perf] Error 2 [Pipeline] sh [2025-05-31T20:59:53.906Z] + uname [2025-05-31T20:59:53.906Z] + [ Linux = AIX ] [2025-05-31T20:59:53.906Z] + uname [2025-05-31T20:59:53.906Z] + [ Linux = SunOS ] [2025-05-31T20:59:53.906Z] + uname [2025-05-31T20:59:53.906Z] + [ Linux = *BSD ] [2025-05-31T20:59:53.906Z] + MAKE=make [2025-05-31T20:59:53.906Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-05-31T20:59:53.906Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-05-31T20:59:54.298Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-05-31T20:59:54.755Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-05-31T20:59:54.965Z] TAP Reports Processing: START [2025-05-31T20:59:54.965Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-05-31T20:59:55.739Z] Saving reports... [2025-05-31T20:59:56.003Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/168/tap-master-files/aqa-tests/TKG/output_17487251369377/Test_openjdk8_hs_extended.perf_arm_linux.tap' [2025-05-31T20:59:56.003Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/168/tap-master-files/aqa-tests/TKG/output_17487251369377/Test_openjdk8_hs_extended.perf_arm_linux.tap]. [2025-05-31T20:59:56.006Z] There are failed test cases. Marking build as UNSTABLE [2025-05-31T20:59:56.006Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-05-31T20:59:56.015Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-05-31T20:59:56.155Z] Archiving artifacts [2025-05-31T20:59:56.426Z] Recording fingerprints [Pipeline] echo [2025-05-31T20:59:56.582Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-05-31T20:59:56.719Z] Archiving artifacts [2025-05-31T20:59:57.006Z] Recording fingerprints [Pipeline] sh [2025-05-31T20:59:58.619Z] + tar -cf benchmark_test_output.tar.gz ./aqa-tests/TKG/output_17487251369377 [Pipeline] echo [2025-05-31T20:59:59.012Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-05-31T20:59:59.151Z] Archiving artifacts [2025-05-31T21:00:01.370Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-05-31T21:00:02.367Z] Tap file found: aqa-tests/TKG/output_17487251369377/Test_openjdk8_hs_extended.perf_arm_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-05-31T21:00:02.567Z] 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=483&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-05-31T21:00:02.709Z] Recording test results [2025-05-31T21:00:03.051Z] None of the test reports contained any result [2025-05-31T21:00:03.052Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-05-31T21:00:03.098Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-05-31T21:00:02.956Z] No test report files were found. Configuration error? [2025-05-31T21:00:04.538Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-05-31T21:00:04.538Z] Unix type machine.. [2025-05-31T21:00:04.538Z] Running on a Linux host [2025-05-31T21:00:04.538Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-05-31T21:00:05.197Z] [WS-CLEANUP] Deleting project workspace... [2025-05-31T21:00:05.197Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-31T21:00:06.573Z] [WS-CLEANUP] done [Pipeline] sh [2025-05-31T21:00:08.018Z] + find /tmp -name *core* -print -exec rm -f {} ; [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-05-31T21:00:08.460Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-05-31T21:00:08.624Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-05-31T21:00:08.658Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-05-31T21:00:08.695Z] Running on test-docker-ubuntu1804-armv8l-4 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] cleanWs [2025-05-31T21:00:08.979Z] [WS-CLEANUP] Deleting project workspace... [2025-05-31T21:00:08.979Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-31T21:00:09.109Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-05-31T21:00:09.523Z] [WS-CLEANUP] Deleting project workspace... [2025-05-31T21:00:09.523Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-31T21:00:09.652Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-05-31T21:00:09.763Z] allocate a node for generating rerun job ... [Pipeline] node [2025-05-31T21:00:09.789Z] Running on test-osuosl-aix72-ppc64-6 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] echo [2025-05-31T21:00:09.809Z] 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-05-31T21:00:09.832Z] 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-05-31T21:00:14.733Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-05-31T21:00:15.959Z] Processing DSL script testJobTemplate [2025-05-31T21:04:59.754Z] LEVELS: [extended] [2025-05-31T21:04:59.754Z] JDK_VERSIONS: [8] [2025-05-31T21:04:59.755Z] GROUPS: [perf] [2025-05-31T21:04:59.755Z] ARCH_OS_LIST: [arm_linux] [2025-05-31T21:04:59.897Z] Added items: [2025-05-31T21:04:59.897Z] GeneratedJob{name='Test_openjdk8_hs_extended.perf_arm_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-05-31T21:05:00.841Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk8_hs_extended.perf_arm_linux_rerun) [Pipeline] build [2025-05-31T21:05:00.865Z] Scheduling project: Test_openjdk8_hs_extended.perf_arm_linux_rerun [2025-05-31T21:05:06.247Z] Starting building: Test_openjdk8_hs_extended.perf_arm_linux_rerun #3 [2025-05-31T21:27:06.367Z] Build Test_openjdk8_hs_extended.perf_arm_linux_rerun #3 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-05-31T21:27:06.452Z] Running on test-aws-rhel76-armv8-1 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_arm_linux [Pipeline] { [Pipeline] cleanWs [2025-05-31T21:27:06.542Z] [WS-CLEANUP] Deleting project workspace... [2025-05-31T21:27:06.542Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-31T21:27:06.577Z] [WS-CLEANUP] done [Pipeline] echo [2025-05-31T21:27:06.585Z] Test_openjdk8_hs_extended.perf_arm_linux_rerun #3 completed with status UNSTABLE [Pipeline] timeout [2025-05-31T21:27:06.587Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-05-31T21:27:06.839Z] Copied 1 artifact from "Test_openjdk8_hs_extended.perf_arm_linux_rerun" build number 3 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-05-31T21:27:06.918Z] TAP Reports Processing: START [2025-05-31T21:27:06.919Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_extended.perf_arm_linux_rerun/3/**/*.tap [2025-05-31T21:27:06.951Z] Saving reports... [2025-05-31T21:27:07.015Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/168/tap-master-files/Test_openjdk8_hs_extended.perf_arm_linux_rerun/3/aqa-tests/TKG/output_17487268006842/Test_openjdk8_hs_extended.perf_arm_linux_rerun.tap' [2025-05-31T21:27:07.015Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_arm_linux/builds/168/tap-master-files/Test_openjdk8_hs_extended.perf_arm_linux_rerun/3/aqa-tests/TKG/output_17487268006842/Test_openjdk8_hs_extended.perf_arm_linux_rerun.tap]. [2025-05-31T21:27:07.018Z] There are failed test cases. Marking build as UNSTABLE [2025-05-31T21:27:07.038Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-05-31T21:27:07.047Z] Saving Test_openjdk8_hs_extended.perf_arm_linux_rerun/3/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-05-31T21:27:07.087Z] Archiving artifacts [2025-05-31T21:27:07.155Z] 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. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? 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-05-31T21:27:07.572Z] [WS-CLEANUP] Deleting project workspace... [2025-05-31T21:27:07.572Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-31T21:27:07.605Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE