[2025-05-23T01:55:37.616Z] make[5]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/functional/MBCS_Tests/urlclassloader' [2025-05-23T01:55:37.616Z] make[4]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/functional/MBCS_Tests' [2025-05-23T01:55:37.616Z] make[3]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/functional' [2025-05-23T01:55:37.616Z] make[2]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests' [2025-05-23T01:55:37.616Z] [2025-05-23T01:55:37.616Z] [2025-05-23T01:55:37.616Z] All tests finished, run result summary: [2025-05-23T01:55:37.616Z] cd "C:/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/\\TKG\\scripts"; \ [2025-05-23T01:55:37.616Z] perl "resultsSum.pl" --failuremk="C:/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/\\TKG\\failedtargets.mk" --resultFile="C:/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/\\TKG\\output_17479648606113\\TestTargetResult" --platFile="C:/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/\\TKG\\resources\\buildPlatformMap.properties" --diagnostic=failure --jdkVersion=25 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=win_x86-64 --buildList=functional --customTarget="" --testTarget=special.functional --tapPath=C:/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/\\TKG\\output_17479648606113\\ --tapName=Test_openjdk25_hs_special.functional_x86-64_windows.tap --comment="" [2025-05-23T01:55:37.616Z] [2025-05-23T01:55:37.616Z] [2025-05-23T01:55:37.616Z] TEST TARGETS SUMMARY [2025-05-23T01:55:37.616Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-05-23T01:55:37.616Z] DISABLED test targets: [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_zh_TW_linux_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_Zh_TW_aix_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_zh_TW_aix_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_ZH_TW_aix_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_i18n_ko_KR_linux_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_i18n_ko_KR_aix_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_i18n_KO_KR_aix_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_locale_matching_zh_CN_aix_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_locale_matching_Zh_CN_aix_0 [2025-05-23T01:55:37.616Z] [2025-05-23T01:55:37.616Z] PASSED test targets: [2025-05-23T01:55:37.616Z] MBCS_Tests_annotation_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_charsets_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_codepage_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_codepage_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_codepage_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_codepage_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_codepage_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_codepoint_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_coin_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_coin_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_coin_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_coin_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_coin_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_compact_number_format_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_Compiler_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_datetime_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_datetime_formatter_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_env_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_file_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_file_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_file_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_file_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_file_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_formatter_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_i18n_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_IDN_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_IDN_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_IDN_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_IDN_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_IDN_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jaxp14_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jaxp14_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jaxp14_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jaxp14_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jaxp14_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jdbc41_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jdbc41_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jdbc41_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jdbc41_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_jdbc41_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_locale_matching_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_locale_matching_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_locale_matching_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_locale_matching_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_locale_matching_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_new_jp_era_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_nio_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_nio_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_nio_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_nio_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_nio_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_pattern_matching_instanceof_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_pref_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_pref_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_pref_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_pref_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_pref_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_property_utf8_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_record_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_regex_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_regex_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_regex_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_regex_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_regex_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_scanner_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_scanner_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_scanner_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_scanner_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_scanner_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_sealed_classes_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_StAX_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_StAX_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_StAX_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_StAX_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_StAX_tw_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_switch_expressions_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_text_blocks_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_unicode_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_urlclassloader_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_urlclassloader_ja_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_urlclassloader_ko_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_urlclassloader_cn_windows_0 [2025-05-23T01:55:37.616Z] MBCS_Tests_urlclassloader_tw_windows_0 [2025-05-23T01:55:37.616Z] [2025-05-23T01:55:37.616Z] FAILED test targets: [2025-05-23T01:55:37.616Z] MBCS_Tests_language_tag_0 [2025-05-23T01:55:37.616Z] [2025-05-23T01:55:37.616Z] TOTAL: 452 EXECUTED: 87 PASSED: 86 FAILED: 1 DISABLED: 10 SKIPPED: 355 [2025-05-23T01:55:37.616Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-05-23T01:55:37.616Z] [2025-05-23T01:55:37.616Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-05-23T01:55:37.616Z] make[1]: Leaving directory '/cygdrive/c/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows/aqa-tests/TKG' [2025-05-23T01:55:37.616Z] make: *** [makefile:66: _special.functional] Error 2 [Pipeline] sh [2025-05-23T01:55:38.127Z] ++ uname [2025-05-23T01:55:38.127Z] + '[' CYGWIN_NT-10.0-20348 = AIX ']' [2025-05-23T01:55:38.127Z] ++ uname [2025-05-23T01:55:38.456Z] + '[' CYGWIN_NT-10.0-20348 = SunOS ']' [2025-05-23T01:55:38.456Z] ++ uname [2025-05-23T01:55:38.456Z] + '[' CYGWIN_NT-10.0-20348 = '*BSD' ']' [2025-05-23T01:55:38.456Z] + MAKE=make [2025-05-23T01:55:38.456Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-05-23T01:55:38.456Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] echo [2025-05-23T01:55:38.579Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-05-23T01:55:38.679Z] TAP Reports Processing: START [2025-05-23T01:55:38.680Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-05-23T01:55:38.735Z] Saving reports... [2025-05-23T01:55:38.773Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_x86-64_windows/builds/10/tap-master-files/aqa-tests/TKG/output_17479648606113/Test_openjdk25_hs_special.functional_x86-64_windows.tap' [2025-05-23T01:55:38.773Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_x86-64_windows/builds/10/tap-master-files/aqa-tests/TKG/output_17479648606113/Test_openjdk25_hs_special.functional_x86-64_windows.tap]. [2025-05-23T01:55:38.791Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-05-23T01:55:38.799Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-05-23T01:55:38.828Z] Archiving artifacts [2025-05-23T01:55:38.869Z] Recording fingerprints [Pipeline] echo [2025-05-23T01:55:38.912Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-05-23T01:55:38.943Z] Archiving artifacts [2025-05-23T01:55:39.009Z] Recording fingerprints [Pipeline] sh [2025-05-23T01:55:39.545Z] + tar -cf - ./aqa-tests/TKG/output_17479648606113 [2025-05-23T01:55:39.545Z] + pigz -9 [2025-05-23T01:55:39.545Z] + gzip -9 [Pipeline] echo [2025-05-23T01:55:40.317Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-05-23T01:55:40.346Z] Archiving artifacts [2025-05-23T01:55:40.390Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-05-23T01:55:41.154Z] Tap file found: aqa-tests\TKG\output_17479648606113\Test_openjdk25_hs_special.functional_x86-64_windows.tap... [Pipeline] readFile [Pipeline] echo [2025-05-23T01:55:41.666Z] Rerun in Grinder with failed test targets: https://ci.adoptium.net/job/Grinder/parambuild/?SDK_RESOURCE=upstream&TARGET=testList+TESTLIST=MBCS_Tests_language_tag_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=25&DOCKER_REGISTRY_URL=&ITERATIONS=1&VENDOR_TEST_REPOS=&JDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Fjdk&JCK_GIT_BRANCH=master&OPENJ9_BRANCH=master&OPENJ9_SHA=&JCK_GIT_REPO=&VENDOR_TEST_BRANCHES=&UPSTREAM_JOB_NAME=build-scripts%2Fjobs%2Fjdk%2Fjdk-windows-x64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk-25%2B24_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=true&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=functional&ADDITIONAL_ARTIFACTS_REQUIRED=&UPSTREAM_JOB_NUMBER=438&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-05-23T01:55:41.708Z] Recording test results [2025-05-23T01:55:42.405Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-05-23T01:55:42.467Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-05-23T01:55:42.927Z] + aqa-tests/terminateTestProcesses.sh null [2025-05-23T01:55:42.927Z] Windows machine, using powershell queries... [2025-05-23T01:55:43.635Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-05-23T01:55:43.743Z] [WS-CLEANUP] Deleting project workspace... [2025-05-23T01:55:43.743Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-23T01:55:49.124Z] [WS-CLEANUP] done [Pipeline] sh [2025-05-23T01:55:49.593Z] + find /cygdrive/c/temp -name '*core*' -print -exec rm -f '{}' ';' [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-05-23T01:55:49.725Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-05-23T01:55:49.972Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-05-23T01:55:50.056Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-05-23T01:55:50.132Z] Running on test-ibmcloud-ubuntu1604-x64-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows [Pipeline] { [Pipeline] cleanWs [2025-05-23T01:55:50.383Z] [WS-CLEANUP] Deleting project workspace... [2025-05-23T01:55:50.383Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-23T01:55:50.495Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-05-23T01:55:50.842Z] [WS-CLEANUP] Deleting project workspace... [2025-05-23T01:55:50.842Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-23T01:55:50.950Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-05-23T01:55:51.088Z] allocate a node for generating rerun job ... [Pipeline] node [2025-05-23T01:55:51.129Z] Running on test-docker-ubi9-armv8l-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows [Pipeline] { [Pipeline] echo [2025-05-23T01:55:51.161Z] Generating rerun Test_openjdk25_hs_special.functional_x86-64_windows_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.functional_x86-64_windows_rerun) [Pipeline] echo [2025-05-23T01:55:51.212Z] GENERATE_JOBS is set to true, set test job Test_openjdk25_hs_special.functional_x86-64_windows_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-05-23T01:55:52.949Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-05-23T01:55:54.002Z] Processing DSL script testJobTemplate [2025-05-23T01:59:19.692Z] LEVELS: [special] [2025-05-23T01:59:19.692Z] JDK_VERSIONS: [8] [2025-05-23T01:59:19.692Z] GROUPS: [functional] [2025-05-23T01:59:19.692Z] ARCH_OS_LIST: [x86-64_windows] [2025-05-23T01:59:19.837Z] Added items: [2025-05-23T01:59:19.838Z] GeneratedJob{name='Test_openjdk25_hs_special.functional_x86-64_windows_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-05-23T01:59:20.839Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.functional_x86-64_windows_rerun) [Pipeline] build [2025-05-23T01:59:20.873Z] Scheduling project: Test_openjdk25_hs_special.functional_x86-64_windows_rerun [2025-05-23T01:59:30.429Z] Starting building: Test_openjdk25_hs_special.functional_x86-64_windows_rerun #9 [2025-05-24T04:03:19.558Z] Build Test_openjdk25_hs_special.functional_x86-64_windows_rerun #9 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-05-24T04:03:19.634Z] Running on test-rhibmcloud-rhel9-x64-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_x86-64_windows [Pipeline] { [Pipeline] cleanWs [2025-05-24T04:03:19.695Z] [WS-CLEANUP] Deleting project workspace... [2025-05-24T04:03:19.695Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-24T04:03:19.715Z] [WS-CLEANUP] done [Pipeline] echo [2025-05-24T04:03:19.725Z] Test_openjdk25_hs_special.functional_x86-64_windows_rerun #9 completed with status UNSTABLE [Pipeline] timeout [2025-05-24T04:03:19.728Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-05-24T04:03:19.901Z] Copied 1 artifact from "Test_openjdk25_hs_special.functional_x86-64_windows_rerun" build number 9 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-05-24T04:03:19.993Z] TAP Reports Processing: START [2025-05-24T04:03:19.993Z] Looking for TAP results report in workspace using pattern: Test_openjdk25_hs_special.functional_x86-64_windows_rerun/9/**/*.tap [2025-05-24T04:03:20.375Z] Saving reports... [2025-05-24T04:03:20.640Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_x86-64_windows/builds/10/tap-master-files/Test_openjdk25_hs_special.functional_x86-64_windows_rerun/9/aqa-tests/TKG/output_17480593804050/Test_openjdk25_hs_special.functional_x86-64_windows_rerun.tap' [2025-05-24T04:03:20.640Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_x86-64_windows/builds/10/tap-master-files/Test_openjdk25_hs_special.functional_x86-64_windows_rerun/9/aqa-tests/TKG/output_17480593804050/Test_openjdk25_hs_special.functional_x86-64_windows_rerun.tap]. [2025-05-24T04:03:20.641Z] org.tap4j.parser.ParserException: Error parsing TAP Stream: Missing TAP Plan. [2025-05-24T04:03:20.641Z] at PluginClassLoader for tap//org.tap4j.parser.Tap13Parser.parseTapStream(Tap13Parser.java:257) [2025-05-24T04:03:20.641Z] at PluginClassLoader for tap//org.tap4j.parser.Tap13Parser.parseFile(Tap13Parser.java:231) [2025-05-24T04:03:20.641Z] at PluginClassLoader for tap//org.tap4j.plugin.TapParser.parse(TapParser.java:172) [2025-05-24T04:03:20.641Z] at PluginClassLoader for tap//org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:475) [2025-05-24T04:03:20.642Z] at PluginClassLoader for tap//org.tap4j.plugin.TapPublisher.performImpl(TapPublisher.java:352) [2025-05-24T04:03:20.642Z] at PluginClassLoader for tap//org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:312) [2025-05-24T04:03:20.642Z] at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123) [2025-05-24T04:03:20.642Z] at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:101) [2025-05-24T04:03:20.642Z] at PluginClassLoader for workflow-basic-steps//org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71) [2025-05-24T04:03:20.642Z] at PluginClassLoader for workflow-step-api//org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:49) [2025-05-24T04:03:20.642Z] at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [2025-05-24T04:03:20.642Z] at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [2025-05-24T04:03:20.642Z] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [2025-05-24T04:03:20.642Z] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [2025-05-24T04:03:20.642Z] at java.base/java.lang.Thread.run(Thread.java:840) [2025-05-24T04:03:20.642Z] Caused by: org.tap4j.parser.ParserException: Missing TAP Plan. [2025-05-24T04:03:20.642Z] at PluginClassLoader for tap//org.tap4j.parser.Tap13Parser.onFinish(Tap13Parser.java:429) [2025-05-24T04:03:20.642Z] at PluginClassLoader for tap//org.tap4j.parser.Tap13Parser.parseTapStream(Tap13Parser.java:255) [2025-05-24T04:03:20.642Z] ... 14 more [2025-05-24T04:03:20.643Z] TAP parse errors found in the build. Marking build as UNSTABLE [2025-05-24T04:03:20.667Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-05-24T04:03:20.677Z] Saving Test_openjdk25_hs_special.functional_x86-64_windows_rerun/9/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-05-24T04:03:20.704Z] Archiving artifacts [2025-05-24T04:03:21.102Z] 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. [Pipeline] cleanWs [2025-05-24T04:03:21.506Z] [WS-CLEANUP] Deleting project workspace... [2025-05-24T04:03:21.506Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-24T04:03:21.526Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE