[2025-06-26T23:50:16.687Z] make[4]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests/perf/renaissance' [2025-06-26T23:50:16.687Z] make[3]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests/perf' [2025-06-26T23:50:16.687Z] make[2]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests' [2025-06-26T23:50:16.687Z] [2025-06-26T23:50:16.687Z] [2025-06-26T23:50:17.011Z] All tests finished, run result summary: [2025-06-26T23:50:17.011Z] cd "C:/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests/\\TKG\\scripts"; \ [2025-06-26T23:50:17.011Z] perl "resultsSum.pl" --failuremk="C:/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests/\\TKG\\failedtargets.mk" --resultFile="C:/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests/\\TKG\\output_17509811014922\\TestTargetResult" --platFile="C:/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests/\\TKG\\resources\\buildPlatformMap.properties" --diagnostic=failure --jdkVersion=21 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=win_x86-64 --buildList=perf --customTarget="" --testTarget=extended.perf --tapPath=C:/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests/\\TKG\\output_17509811014922\\ --tapName=Test_openjdk21_hs_extended.perf_x86-64_windows.tap --comment="" [2025-06-26T23:50:17.011Z] [2025-06-26T23:50:17.011Z] [2025-06-26T23:50:17.011Z] TEST TARGETS SUMMARY [2025-06-26T23:50:17.011Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-26T23:50:17.011Z] DISABLED test targets: [2025-06-26T23:50:17.011Z] dacapo-avrora_0 [2025-06-26T23:50:17.011Z] dacapo-pmd_0 [2025-06-26T23:50:17.011Z] dacapo-tomcat_0 [2025-06-26T23:50:17.011Z] renaissance-finagle-chirper_0 [2025-06-26T23:50:17.011Z] [2025-06-26T23:50:17.011Z] PASSED test targets: [2025-06-26T23:50:17.011Z] dacapo-fop_0 [2025-06-26T23:50:17.011Z] dacapo-jython_0 [2025-06-26T23:50:17.011Z] dacapo-luindex_0 [2025-06-26T23:50:17.011Z] dacapo-sunflow_0 [2025-06-26T23:50:17.011Z] dacapo-xalan_0 [2025-06-26T23:50:17.011Z] renaissance-db-shootout_0 [2025-06-26T23:50:17.011Z] renaissance-finagle-http_0 [2025-06-26T23:50:17.011Z] renaissance-mnemonics_0 [2025-06-26T23:50:17.011Z] renaissance-par-mnemonics_0 [2025-06-26T23:50:17.011Z] renaissance-philosophers_0 [2025-06-26T23:50:17.011Z] [2025-06-26T23:50:17.011Z] FAILED test targets: [2025-06-26T23:50:17.011Z] renaissance-als_0 [2025-06-26T23:50:17.011Z] renaissance-chi-square_0 [2025-06-26T23:50:17.011Z] renaissance-dec-tree_0 [2025-06-26T23:50:17.011Z] renaissance-gauss-mix_0 [2025-06-26T23:50:17.011Z] renaissance-log-regression_0 [2025-06-26T23:50:17.011Z] renaissance-movie-lens_0 [2025-06-26T23:50:17.011Z] [2025-06-26T23:50:17.011Z] TOTAL: 20 EXECUTED: 16 PASSED: 10 FAILED: 6 DISABLED: 4 SKIPPED: 0 [2025-06-26T23:50:17.011Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-26T23:50:17.011Z] [2025-06-26T23:50:17.332Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-26T23:50:17.332Z] make[1]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows/aqa-tests/TKG' [2025-06-26T23:50:17.332Z] make: *** [makefile:62: _extended.perf] Error 2 [Pipeline] sh [2025-06-26T23:50:17.828Z] ++ uname [2025-06-26T23:50:17.828Z] + '[' CYGWIN_NT-10.0-20348 = AIX ']' [2025-06-26T23:50:17.828Z] ++ uname [2025-06-26T23:50:17.828Z] + '[' CYGWIN_NT-10.0-20348 = SunOS ']' [2025-06-26T23:50:18.139Z] ++ uname [2025-06-26T23:50:18.139Z] + '[' CYGWIN_NT-10.0-20348 = '*BSD' ']' [2025-06-26T23:50:18.139Z] + MAKE=make [2025-06-26T23:50:18.139Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-26T23:50:18.139Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-26T23:50:18.187Z] $ ssh-agent -k [2025-06-26T23:50:18.243Z] unset SSH_AUTH_SOCK; [2025-06-26T23:50:18.243Z] unset SSH_AGENT_PID; [2025-06-26T23:50:18.243Z] echo Agent pid 1939 killed; [2025-06-26T23:50:18.295Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] echo [2025-06-26T23:50:18.336Z] no DaCapo-h2 metric found [Pipeline] echo [2025-06-26T23:50:18.373Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-26T23:50:18.465Z] TAP Reports Processing: START [2025-06-26T23:50:18.465Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-26T23:50:18.598Z] Saving reports... [2025-06-26T23:50:18.644Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_extended.perf_x86-64_windows/builds/94/tap-master-files/aqa-tests/TKG/output_17509811014922/Test_openjdk21_hs_extended.perf_x86-64_windows.tap' [2025-06-26T23:50:18.644Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_extended.perf_x86-64_windows/builds/94/tap-master-files/aqa-tests/TKG/output_17509811014922/Test_openjdk21_hs_extended.perf_x86-64_windows.tap]. [2025-06-26T23:50:18.649Z] There are failed test cases. Marking build as UNSTABLE [2025-06-26T23:50:18.649Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-26T23:50:18.656Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T23:50:18.684Z] Archiving artifacts [2025-06-26T23:50:18.723Z] Recording fingerprints [Pipeline] echo [2025-06-26T23:50:18.764Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-26T23:50:18.791Z] Archiving artifacts [2025-06-26T23:50:18.903Z] Recording fingerprints [Pipeline] sh [2025-06-26T23:50:19.462Z] + tar -cf benchmark_test_output.tar.gz ./aqa-tests/TKG/output_17509811014922 [Pipeline] echo [2025-06-26T23:50:59.201Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-26T23:50:59.229Z] Archiving artifacts [2025-06-26T23:53:05.840Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-26T23:53:10.539Z] Tap file found: aqa-tests\TKG\output_17509811014922\Test_openjdk21_hs_extended.perf_x86-64_windows.tap... [Pipeline] readFile [Pipeline] echo [2025-06-26T23:53:10.684Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=renaissance-als_0,renaissance-chi-square_0,renaissance-dec-tree_0,renaissance-gauss-mix_0,renaissance-log-regression_0,renaissance-movie-lens_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-64_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=21&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk21u&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk21u%2Fjdk21u-windows-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=dev&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=283&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-26T23:53:10.719Z] Recording test results [2025-06-26T23:53:11.540Z] None of the test reports contained any result [2025-06-26T23:53:11.541Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T23:53:11.593Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-26T23:53:11.500Z] No test report files were found. Configuration error? [2025-06-26T23:53:12.036Z] + aqa-tests/terminateTestProcesses.sh null [2025-06-26T23:53:12.036Z] Windows machine, using powershell queries... [2025-06-26T23:53:13.135Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-26T23:53:13.224Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T23:53:13.224Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T23:53:23.783Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-26T23:53:24.234Z] + find /cygdrive/c/temp -name '*core*' -print -exec rm -f '{}' ';' [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-26T23:53:24.981Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-26T23:53:25.154Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-26T23:53:25.201Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-26T23:53:25.348Z] Running on test-osuosl-aix72-ppc64-2 in /home/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows [Pipeline] { [Pipeline] cleanWs [2025-06-26T23:53:25.736Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T23:53:25.736Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T23:53:25.909Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-26T23:53:26.454Z] [WS-CLEANUP] Deleting project workspace... [2025-06-26T23:53:26.454Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-26T23:53:26.627Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-26T23:53:26.757Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-26T23:53:26.839Z] Running on test-azure-win11-aarch64-2 in C:\Users\jenkins\workspace\Test_openjdk21_hs_extended.perf_x86-64_windows [Pipeline] { [Pipeline] echo [2025-06-26T23:53:26.865Z] Generating rerun Test_openjdk21_hs_extended.perf_x86-64_windows_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk21_hs_extended.perf_x86-64_windows_rerun) [Pipeline] echo [2025-06-26T23:53:26.914Z] GENERATE_JOBS is set to true, set test job Test_openjdk21_hs_extended.perf_x86-64_windows_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-06-26T23:53:27.423Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-26T23:53:28.194Z] Processing DSL script testJobTemplate [2025-06-26T23:53:59.790Z] LEVELS: [extended] [2025-06-26T23:53:59.790Z] JDK_VERSIONS: [8] [2025-06-26T23:53:59.790Z] GROUPS: [perf] [2025-06-26T23:53:59.790Z] ARCH_OS_LIST: [x86-64_windows] [2025-06-26T23:54:00.002Z] Existing items: [2025-06-26T23:54:00.002Z] GeneratedJob{name='Test_openjdk21_hs_extended.perf_x86-64_windows_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-26T23:54:19.833Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk21_hs_extended.perf_x86-64_windows_rerun) [Pipeline] build [2025-06-26T23:54:19.864Z] Scheduling project: Test_openjdk21_hs_extended.perf_x86-64_windows_rerun [2025-06-26T23:54:25.293Z] Starting building: Test_openjdk21_hs_extended.perf_x86-64_windows_rerun #2 [2025-06-27T03:01:11.098Z] Build Test_openjdk21_hs_extended.perf_x86-64_windows_rerun #2 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-27T03:01:11.209Z] Running on test-docker-ubuntu2404-armv8-3 in /home/jenkins/workspace/Test_openjdk21_hs_extended.perf_x86-64_windows [Pipeline] { [Pipeline] cleanWs [2025-06-27T03:01:11.525Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T03:01:11.525Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T03:01:11.670Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-27T03:01:11.676Z] Test_openjdk21_hs_extended.perf_x86-64_windows_rerun #2 completed with status UNSTABLE [Pipeline] timeout [2025-06-27T03:01:11.678Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-27T03:01:12.696Z] Copied 1 artifact from "Test_openjdk21_hs_extended.perf_x86-64_windows_rerun" build number 2 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-27T03:01:12.899Z] TAP Reports Processing: START [2025-06-27T03:01:12.900Z] Looking for TAP results report in workspace using pattern: Test_openjdk21_hs_extended.perf_x86-64_windows_rerun/2/**/*.tap [2025-06-27T03:01:13.042Z] Saving reports... [2025-06-27T03:01:13.345Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_extended.perf_x86-64_windows/builds/94/tap-master-files/Test_openjdk21_hs_extended.perf_x86-64_windows_rerun/2/aqa-tests/TKG/output_1750993051502/Test_openjdk21_hs_extended.perf_x86-64_windows_rerun.tap' [2025-06-27T03:01:13.345Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk21_hs_extended.perf_x86-64_windows/builds/94/tap-master-files/Test_openjdk21_hs_extended.perf_x86-64_windows_rerun/2/aqa-tests/TKG/output_1750993051502/Test_openjdk21_hs_extended.perf_x86-64_windows_rerun.tap]. [2025-06-27T03:01:13.350Z] There are failed test cases. Marking build as UNSTABLE [2025-06-27T03:01:13.364Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-27T03:01:13.375Z] Saving Test_openjdk21_hs_extended.perf_x86-64_windows_rerun/2/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T03:01:13.523Z] Archiving artifacts [2025-06-27T03:01:13.813Z] 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. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? Script1 seems to be setting a field named match (to a value of type Matcher) which could lead to memory leaks or other issues. Did you forget the `def` keyword? 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-27T03:01:15.402Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T03:01:15.402Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T03:01:15.543Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE