[2025-05-22T23:26:06.896Z] make[5]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/functional/MBCS_Tests/unicode' [2025-05-22T23:26:06.896Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/functional/MBCS_Tests' [2025-05-22T23:26:06.896Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/functional' [2025-05-22T23:26:06.896Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests' [2025-05-22T23:26:06.896Z] [2025-05-22T23:26:06.896Z] [2025-05-22T23:26:06.896Z] All tests finished, run result summary: [2025-05-22T23:26:06.896Z] cd "/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-05-22T23:26:06.896Z] perl "resultsSum.pl" --failuremk="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/TKG/../TKG/failedtargets.mk" --resultFile="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/TKG/../TKG/output_17479547351695/TestTargetResult" --platFile="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/TKG/../TKG/resources/buildPlatformMap.properties" --diagnostic=failure --jdkVersion=25 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=linux_riscv64 --buildList=functional --customTarget="" --testTarget=special.functional --tapPath=/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/TKG/../TKG/output_17479547351695/ --tapName=Test_openjdk25_hs_special.functional_riscv64_linux.tap --comment="" [2025-05-22T23:26:07.238Z] [2025-05-22T23:26:07.238Z] [2025-05-22T23:26:07.238Z] TEST TARGETS SUMMARY [2025-05-22T23:26:07.238Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-05-22T23:26:07.238Z] DISABLED test targets: [2025-05-22T23:26:07.238Z] MBCS_Tests_locale_matching_zh_CN_aix_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_locale_matching_Zh_CN_aix_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_formatter_zh_TW_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_formatter_Zh_TW_aix_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_formatter_zh_TW_aix_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_formatter_ZH_TW_aix_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_formatter_tw_windows_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_i18n_ko_KR_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_i18n_ko_KR_aix_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_i18n_KO_KR_aix_0 [2025-05-22T23:26:07.238Z] [2025-05-22T23:26:07.238Z] PASSED test targets: [2025-05-22T23:26:07.238Z] MBCS_Tests_coin_ja_JP_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_coin_ko_KR_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_coin_zh_CN_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_coin_zh_TW_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_sealed_classes_ja_JP_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_sealed_classes_ko_KR_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_sealed_classes_zh_CN_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_sealed_classes_zh_TW_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_codepoint_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_env_ja_JP_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_env_ko_KR_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_env_zh_CN_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_env_zh_TW_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_locale_matching_ja_JP_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_locale_matching_ko_KR_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_locale_matching_zh_CN_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_locale_matching_zh_TW_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_datetime_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_datetime_formatter_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_StAX_ja_JP_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_StAX_ko_KR_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_StAX_zh_CN_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_StAX_zh_TW_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_jaxp14_ja_JP_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_jaxp14_ko_KR_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_jaxp14_zh_CN_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_jaxp14_zh_TW_linux_0 [2025-05-22T23:26:07.238Z] MBCS_Tests_nio_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_nio_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_nio_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_nio_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_formatter_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_formatter_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_formatter_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_i18n_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_i18n_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_i18n_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_pref_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_pref_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_pref_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_pref_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_codepage_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_codepage_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_codepage_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_codepage_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_compact_number_format_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_compact_number_format_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_compact_number_format_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_compact_number_format_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_urlclassloader_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_urlclassloader_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_urlclassloader_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_urlclassloader_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_new_jp_era_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_record_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_record_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_record_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_record_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_regex_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_regex_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_regex_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_regex_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_scanner_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_scanner_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_scanner_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_scanner_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_IDN_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_IDN_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_IDN_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_IDN_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_pattern_matching_instanceof_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_pattern_matching_instanceof_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_pattern_matching_instanceof_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_pattern_matching_instanceof_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_switch_expressions_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_switch_expressions_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_switch_expressions_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_switch_expressions_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_Compiler_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_Compiler_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_Compiler_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_Compiler_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_charsets_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_property_utf8_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_jdbc41_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_jdbc41_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_jdbc41_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_jdbc41_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_file_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_file_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_file_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_file_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_text_blocks_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_text_blocks_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_text_blocks_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_text_blocks_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_annotation_ja_JP_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_annotation_ko_KR_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_annotation_zh_CN_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_annotation_zh_TW_linux_0 [2025-05-22T23:26:07.239Z] MBCS_Tests_unicode_linux_0 [2025-05-22T23:26:07.239Z] [2025-05-22T23:26:07.239Z] FAILED test targets: [2025-05-22T23:26:07.239Z] MBCS_Tests_language_tag_0 [2025-05-22T23:26:07.239Z] [2025-05-22T23:26:07.239Z] TOTAL: 452 EXECUTED: 102 PASSED: 101 FAILED: 1 DISABLED: 10 SKIPPED: 340 [2025-05-22T23:26:07.239Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-05-22T23:26:07.239Z] [2025-05-22T23:26:07.239Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-05-22T23:26:07.239Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux/aqa-tests/TKG' [2025-05-22T23:26:07.239Z] make: *** [makefile:66: _special.functional] Error 2 [Pipeline] sh [2025-05-22T23:26:07.843Z] + uname [2025-05-22T23:26:07.843Z] + [ Linux = AIX ] [2025-05-22T23:26:07.843Z] + uname [2025-05-22T23:26:07.843Z] + [ Linux = SunOS ] [2025-05-22T23:26:07.843Z] + uname [2025-05-22T23:26:07.843Z] + [ Linux = *BSD ] [2025-05-22T23:26:07.843Z] + MAKE=make [2025-05-22T23:26:07.843Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-05-22T23:26:07.843Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-05-22T23:26:07.910Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-05-22T23:26:08.150Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-05-22T23:26:08.262Z] TAP Reports Processing: START [2025-05-22T23:26:08.263Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-05-22T23:26:08.335Z] Saving reports... [2025-05-22T23:26:08.404Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_riscv64_linux/builds/13/tap-master-files/aqa-tests/TKG/output_17479547351695/Test_openjdk25_hs_special.functional_riscv64_linux.tap' [2025-05-22T23:26:08.404Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_riscv64_linux/builds/13/tap-master-files/aqa-tests/TKG/output_17479547351695/Test_openjdk25_hs_special.functional_riscv64_linux.tap]. [2025-05-22T23:26:08.426Z] There are failed test cases. Marking build as UNSTABLE [2025-05-22T23:26:08.426Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-05-22T23:26:08.435Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-05-22T23:26:08.466Z] Archiving artifacts [2025-05-22T23:26:08.537Z] Recording fingerprints [Pipeline] echo [2025-05-22T23:26:08.572Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-05-22T23:26:08.605Z] Archiving artifacts [2025-05-22T23:26:08.736Z] Recording fingerprints [Pipeline] sh [2025-05-22T23:26:09.336Z] + tar -cf - ./aqa-tests/TKG/output_17479547351695 [2025-05-22T23:26:09.336Z] + pigz -9 [Pipeline] echo [2025-05-22T23:26:09.415Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-05-22T23:26:09.453Z] Archiving artifacts [2025-05-22T23:26:09.578Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-05-22T23:26:10.550Z] Tap file found: aqa-tests/TKG/output_17479547351695/Test_openjdk25_hs_special.functional_riscv64_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-05-22T23:26:11.097Z] 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=riscv64_linux&GENERATE_JOBS=true&KEEP_REPORTDIR=false&PERSONAL_BUILD=false&DOCKER_REGISTRY_DIR=&RERUN_ITERATIONS=0&ADOPTOPENJDK_REPO=https%3A%2F%2Fgithub.com%2Fadoptium%2Faqa-tests.git&SETUP_JCK_RUN=false&DOCKER_REGISTRY_URL_CREDENTIAL_ID=&LABEL=&EXTRA_OPTIONS=&CUSTOMIZED_SDK_URL=&BUILD_IDENTIFIER=&JENKINS_KEY=&ADOPTOPENJDK_BRANCH=master&LIGHT_WEIGHT_CHECKOUT=false&USE_JRE=false&ARTIFACTORY_SERVER=&KEEP_WORKSPACE=false&USER_CREDENTIALS_ID=&JDK_VERSION=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-linux-riscv64-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=205&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-05-22T23:26:11.223Z] Recording test results [2025-05-22T23:26:12.390Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-05-22T23:26:12.476Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-05-22T23:26:12.937Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-05-22T23:26:12.937Z] Unix type machine.. [2025-05-22T23:26:12.937Z] Running on a Linux host [2025-05-22T23:26:12.937Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-05-22T23:26:13.100Z] [WS-CLEANUP] Deleting project workspace... [2025-05-22T23:26:13.100Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-22T23:26:20.101Z] [WS-CLEANUP] done [Pipeline] sh [2025-05-22T23:26:20.633Z] + find /tmp -name *core* -print -exec rm -f {} ; [2025-05-22T23:26:20.633Z] + true [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-05-22T23:26:20.787Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-05-22T23:26:21.110Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-05-22T23:26:21.215Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-05-22T23:26:21.286Z] Running on test-azure-win11-aarch64-1 in C:\Users\jenkins\workspace\Test_openjdk25_hs_special.functional_riscv64_linux [Pipeline] { [Pipeline] cleanWs [2025-05-22T23:26:21.453Z] [WS-CLEANUP] Deleting project workspace... [2025-05-22T23:26:21.453Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-22T23:26:21.477Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-05-22T23:26:21.555Z] [WS-CLEANUP] Deleting project workspace... [2025-05-22T23:26:21.555Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-22T23:26:21.571Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-05-22T23:26:21.762Z] allocate a node for generating rerun job ... [Pipeline] node [2025-05-22T23:26:21.799Z] Running on test-azure-win11-aarch64-1 in C:\Users\jenkins\workspace\Test_openjdk25_hs_special.functional_riscv64_linux [Pipeline] { [Pipeline] echo [2025-05-22T23:26:21.854Z] Generating rerun Test_openjdk25_hs_special.functional_riscv64_linux_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.functional_riscv64_linux_rerun) [Pipeline] echo [2025-05-22T23:26:21.934Z] GENERATE_JOBS is set to true, set test job Test_openjdk25_hs_special.functional_riscv64_linux_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-05-22T23:26:22.484Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-05-22T23:26:23.251Z] Processing DSL script testJobTemplate [2025-05-22T23:26:51.471Z] LEVELS: [special] [2025-05-22T23:26:51.471Z] JDK_VERSIONS: [8] [2025-05-22T23:26:51.471Z] GROUPS: [functional] [2025-05-22T23:26:51.471Z] ARCH_OS_LIST: [riscv64_linux] [2025-05-22T23:26:51.634Z] Existing items: [2025-05-22T23:26:51.634Z] GeneratedJob{name='Test_openjdk25_hs_special.functional_riscv64_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-05-22T23:26:52.790Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.functional_riscv64_linux_rerun) [Pipeline] build [2025-05-22T23:26:52.834Z] Scheduling project: Test_openjdk25_hs_special.functional_riscv64_linux_rerun [2025-05-22T23:27:00.412Z] Starting building: Test_openjdk25_hs_special.functional_riscv64_linux_rerun #13 [2025-05-23T07:04:15.293Z] Build Test_openjdk25_hs_special.functional_riscv64_linux_rerun #13 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-05-23T07:04:15.403Z] Running on test-docker-alpine319-armv8-2 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_riscv64_linux [Pipeline] { [Pipeline] cleanWs [2025-05-23T07:04:15.733Z] [WS-CLEANUP] Deleting project workspace... [2025-05-23T07:04:15.733Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-23T07:04:15.885Z] [WS-CLEANUP] done [Pipeline] echo [2025-05-23T07:04:15.893Z] Test_openjdk25_hs_special.functional_riscv64_linux_rerun #13 completed with status UNSTABLE [Pipeline] timeout [2025-05-23T07:04:15.895Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-05-23T07:04:16.864Z] Copied 1 artifact from "Test_openjdk25_hs_special.functional_riscv64_linux_rerun" build number 13 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-05-23T07:04:17.080Z] TAP Reports Processing: START [2025-05-23T07:04:17.081Z] Looking for TAP results report in workspace using pattern: Test_openjdk25_hs_special.functional_riscv64_linux_rerun/13/**/*.tap [2025-05-23T07:04:17.218Z] Saving reports... [2025-05-23T07:04:17.485Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_riscv64_linux/builds/13/tap-master-files/Test_openjdk25_hs_special.functional_riscv64_linux_rerun/13/aqa-tests/TKG/output_17479838364793/Test_openjdk25_hs_special.functional_riscv64_linux_rerun.tap' [2025-05-23T07:04:17.485Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_riscv64_linux/builds/13/tap-master-files/Test_openjdk25_hs_special.functional_riscv64_linux_rerun/13/aqa-tests/TKG/output_17479838364793/Test_openjdk25_hs_special.functional_riscv64_linux_rerun.tap]. [2025-05-23T07:04:17.491Z] There are failed test cases. Marking build as UNSTABLE [2025-05-23T07:04:17.519Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-05-23T07:04:17.528Z] Saving Test_openjdk25_hs_special.functional_riscv64_linux_rerun/13/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-05-23T07:04:17.667Z] Archiving artifacts [2025-05-23T07:04:17.959Z] 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-23T07:04:19.496Z] [WS-CLEANUP] Deleting project workspace... [2025-05-23T07:04:19.496Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-05-23T07:04:19.631Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE