[2025-06-27T01:19:06.334Z] make[4]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests/perf/renaissance' [2025-06-27T01:19:06.334Z] make[3]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests/perf' [2025-06-27T01:19:06.334Z] make[2]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests' [2025-06-27T01:19:06.334Z] [2025-06-27T01:19:06.334Z] [2025-06-27T01:19:06.334Z] All tests finished, run result summary: [2025-06-27T01:19:06.334Z] cd "C:/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests/\\TKG\\scripts"; \ [2025-06-27T01:19:06.334Z] perl "resultsSum.pl" --failuremk="C:/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests/\\TKG\\failedtargets.mk" --resultFile="C:/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests/\\TKG\\output_17509870039333\\TestTargetResult" --platFile="C:/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests/\\TKG\\resources\\buildPlatformMap.properties" --diagnostic=failure --jdkVersion=8 --jdkImpl=hotspot --jdkVendor="temurin" --spec=win_x86 --buildList=perf --customTarget="" --testTarget=extended.perf --tapPath=C:/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests/\\TKG\\output_17509870039333\\ --tapName=Test_openjdk8_hs_extended.perf_x86-32_windows.tap --comment="" [2025-06-27T01:19:06.660Z] [2025-06-27T01:19:06.660Z] [2025-06-27T01:19:06.660Z] TEST TARGETS SUMMARY [2025-06-27T01:19:06.660Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-27T01:19:06.660Z] DISABLED test targets: [2025-06-27T01:19:06.660Z] dacapo-luindex_0 [2025-06-27T01:19:06.660Z] dacapo-tomcat_0 [2025-06-27T01:19:06.660Z] renaissance-als_0 [2025-06-27T01:19:06.660Z] renaissance-chi-square_0 [2025-06-27T01:19:06.660Z] renaissance-dec-tree_0 [2025-06-27T01:19:06.660Z] renaissance-finagle-chirper_0 [2025-06-27T01:19:06.660Z] renaissance-gauss-mix_0 [2025-06-27T01:19:06.660Z] renaissance-log-regression_0 [2025-06-27T01:19:06.660Z] renaissance-movie-lens_0 [2025-06-27T01:19:06.660Z] [2025-06-27T01:19:06.660Z] PASSED test targets: [2025-06-27T01:19:06.660Z] dacapo-avrora_0 [2025-06-27T01:19:06.660Z] dacapo-fop_0 [2025-06-27T01:19:06.660Z] dacapo-sunflow_0 [2025-06-27T01:19:06.660Z] dacapo-xalan_0 [2025-06-27T01:19:06.660Z] renaissance-db-shootout_0 [2025-06-27T01:19:06.660Z] renaissance-finagle-http_0 [2025-06-27T01:19:06.660Z] renaissance-mnemonics_0 [2025-06-27T01:19:06.660Z] renaissance-par-mnemonics_0 [2025-06-27T01:19:06.660Z] renaissance-philosophers_0 [2025-06-27T01:19:06.660Z] [2025-06-27T01:19:06.660Z] FAILED test targets: [2025-06-27T01:19:06.660Z] dacapo-jython_0 [2025-06-27T01:19:06.660Z] dacapo-pmd_0 [2025-06-27T01:19:06.660Z] [2025-06-27T01:19:06.660Z] TOTAL: 20 EXECUTED: 11 PASSED: 9 FAILED: 2 DISABLED: 9 SKIPPED: 0 [2025-06-27T01:19:06.660Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-27T01:19:06.660Z] [2025-06-27T01:19:06.660Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-27T01:19:06.660Z] make[1]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows/aqa-tests/TKG' [2025-06-27T01:19:06.660Z] make: *** [makefile:62: _extended.perf] Error 2 [Pipeline] sh [2025-06-27T01:19:07.167Z] ++ uname [2025-06-27T01:19:07.167Z] + '[' CYGWIN_NT-10.0-20348 = AIX ']' [2025-06-27T01:19:07.167Z] ++ uname [2025-06-27T01:19:07.167Z] + '[' CYGWIN_NT-10.0-20348 = SunOS ']' [2025-06-27T01:19:07.167Z] ++ uname [2025-06-27T01:19:07.167Z] + '[' CYGWIN_NT-10.0-20348 = '*BSD' ']' [2025-06-27T01:19:07.167Z] + MAKE=make [2025-06-27T01:19:07.167Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-27T01:19:07.167Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-27T01:19:07.220Z] $ ssh-agent -k [2025-06-27T01:19:07.268Z] unset SSH_AUTH_SOCK; [2025-06-27T01:19:07.268Z] unset SSH_AGENT_PID; [2025-06-27T01:19:07.268Z] echo Agent pid 1391 killed; [2025-06-27T01:19:07.318Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] echo [2025-06-27T01:19:07.355Z] no DaCapo-h2 metric found [Pipeline] echo [2025-06-27T01:19:07.394Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-27T01:19:07.497Z] TAP Reports Processing: START [2025-06-27T01:19:07.498Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-27T01:19:07.547Z] Saving reports... [2025-06-27T01:19:07.587Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_x86-32_windows/builds/199/tap-master-files/aqa-tests/TKG/output_17509870039333/Test_openjdk8_hs_extended.perf_x86-32_windows.tap' [2025-06-27T01:19:07.587Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_x86-32_windows/builds/199/tap-master-files/aqa-tests/TKG/output_17509870039333/Test_openjdk8_hs_extended.perf_x86-32_windows.tap]. [2025-06-27T01:19:07.592Z] There are failed test cases. Marking build as UNSTABLE [2025-06-27T01:19:07.592Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-27T01:19:07.601Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T01:19:07.629Z] Archiving artifacts [2025-06-27T01:19:07.672Z] Recording fingerprints [Pipeline] echo [2025-06-27T01:19:07.716Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T01:19:07.745Z] Archiving artifacts [2025-06-27T01:19:07.814Z] Recording fingerprints [Pipeline] sh [2025-06-27T01:19:08.340Z] + tar -cf benchmark_test_output.tar.gz ./aqa-tests/TKG/output_17509870039333 [Pipeline] echo [2025-06-27T01:19:09.084Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-27T01:19:09.118Z] Archiving artifacts [2025-06-27T01:19:09.205Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-27T01:19:10.137Z] Tap file found: aqa-tests\TKG\output_17509870039333\Test_openjdk8_hs_extended.perf_x86-32_windows.tap... [Pipeline] readFile [Pipeline] echo [2025-06-27T01:19:10.277Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=dacapo-jython_0,dacapo-pmd_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=x86-32_windows&GENERATE_JOBS=true&KEEP_REPORTDIR=false&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=master&LIGHT_WEIGHT_CHECKOUT=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=8&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk8u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk8u%2Fjdk8u-windows-x86-32-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk8u462-b07_adopt&LABEL_ADDITION=&ARTIFACTORY_REPO=&ARTIFACTORY_ROOT_DIR=&UPSTREAM_TEST_JOB_NUMBER=&DOCKERIMAGE_TAG=&TEST_TIME=120&JDK_IMPL=hotspot&SSH_AGENT_CREDENTIAL=&AUTO_DETECT=true&SLACK_CHANNEL=aqavit-bot&DYNAMIC_COMPILE=false&RELATED_NODES=&ADOPTOPENJDK_SYSTEMTEST_OWNER_BRANCH=adoptium%3Amaster&APPLICATION_OPTIONS=&CUSTOMIZED_SDK_URL_CREDENTIAL_ID=eclipse_temurin_bot_email_and_token&ARCHIVE_TEST_RESULTS=false&NUM_MACHINES=&OPENJDK_SHA=&TRSS_URL=&RERUN_FAILURE=false&USE_TESTENV_PROPERTIES=false&BUILD_LIST=perf&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=515&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-27T01:19:10.363Z] Recording test results [2025-06-27T01:19:11.196Z] None of the test reports contained any result [2025-06-27T01:19:11.197Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-27T01:19:11.241Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-27T01:19:11.160Z] No test report files were found. Configuration error? [2025-06-27T01:19:11.730Z] + aqa-tests/terminateTestProcesses.sh null [2025-06-27T01:19:11.730Z] Windows machine, using powershell queries... [2025-06-27T01:19:12.043Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-27T01:19:12.153Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T01:19:12.153Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T01:19:18.692Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-27T01:19:19.174Z] + find /cygdrive/c/temp -name '*core*' -print -exec rm -f '{}' ';' [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-27T01:19:19.258Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-27T01:19:19.502Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-27T01:19:19.537Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-27T01:19:19.651Z] Running on test-azure-win11-aarch64-1 in C:\Users\jenkins\workspace\Test_openjdk8_hs_extended.perf_x86-32_windows [Pipeline] { [Pipeline] cleanWs [2025-06-27T01:19:19.730Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T01:19:19.730Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T01:19:19.758Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-27T01:19:19.845Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T01:19:19.845Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T01:19:19.859Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-27T01:19:19.968Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-27T01:19:20.054Z] Running on test-ibmcloud-rhel6-x64-1 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows [Pipeline] { [Pipeline] echo [2025-06-27T01:19:20.069Z] Generating rerun Test_openjdk8_hs_extended.perf_x86-32_windows_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk8_hs_extended.perf_x86-32_windows_rerun) [Pipeline] echo [2025-06-27T01:19:20.093Z] GENERATE_JOBS is set to true, set test job Test_openjdk8_hs_extended.perf_x86-32_windows_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-06-27T01:19:21.548Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-27T01:19:22.418Z] Processing DSL script testJobTemplate [2025-06-27T01:22:12.805Z] LEVELS: [extended] [2025-06-27T01:22:12.805Z] JDK_VERSIONS: [8] [2025-06-27T01:22:12.805Z] GROUPS: [perf] [2025-06-27T01:22:12.805Z] ARCH_OS_LIST: [x86-32_windows] [2025-06-27T01:22:12.984Z] Added items: [2025-06-27T01:22:12.984Z] GeneratedJob{name='Test_openjdk8_hs_extended.perf_x86-32_windows_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-27T01:22:17.348Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk8_hs_extended.perf_x86-32_windows_rerun) [Pipeline] build [2025-06-27T01:22:17.375Z] Scheduling project: Test_openjdk8_hs_extended.perf_x86-32_windows_rerun [2025-06-27T01:22:26.834Z] Starting building: Test_openjdk8_hs_extended.perf_x86-32_windows_rerun #1 [2025-06-27T08:09:07.938Z] Build Test_openjdk8_hs_extended.perf_x86-32_windows_rerun #1 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-27T08:09:08.059Z] Running on test-osuosl-ubuntu2404-ppc64le-1 in /home/jenkins/workspace/Test_openjdk8_hs_extended.perf_x86-32_windows [Pipeline] { [Pipeline] cleanWs [2025-06-27T08:09:08.439Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T08:09:08.440Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T08:09:08.617Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-27T08:09:08.629Z] Test_openjdk8_hs_extended.perf_x86-32_windows_rerun #1 completed with status UNSTABLE [Pipeline] timeout [2025-06-27T08:09:08.631Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-27T08:09:09.872Z] Copied 1 artifact from "Test_openjdk8_hs_extended.perf_x86-32_windows_rerun" build number 1 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-27T08:09:10.106Z] TAP Reports Processing: START [2025-06-27T08:09:10.107Z] Looking for TAP results report in workspace using pattern: Test_openjdk8_hs_extended.perf_x86-32_windows_rerun/1/**/*.tap [2025-06-27T08:09:10.282Z] Saving reports... [2025-06-27T08:09:10.631Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_x86-32_windows/builds/199/tap-master-files/Test_openjdk8_hs_extended.perf_x86-32_windows_rerun/1/aqa-tests/TKG/output_17510116759507/Test_openjdk8_hs_extended.perf_x86-32_windows_rerun.tap' [2025-06-27T08:09:10.631Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk8_hs_extended.perf_x86-32_windows/builds/199/tap-master-files/Test_openjdk8_hs_extended.perf_x86-32_windows_rerun/1/aqa-tests/TKG/output_17510116759507/Test_openjdk8_hs_extended.perf_x86-32_windows_rerun.tap]. [2025-06-27T08:09:10.635Z] There are failed test cases. Marking build as UNSTABLE [2025-06-27T08:09:10.651Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-27T08:09:10.659Z] Saving Test_openjdk8_hs_extended.perf_x86-32_windows_rerun/1/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T08:09:10.838Z] Archiving artifacts [2025-06-27T08:09:11.196Z] 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. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? 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-27T08:09:12.825Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T08:09:12.825Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T08:09:12.998Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE