[2025-06-27T05:06:52.130Z] make[5]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/functional/MBCS_Tests/language_tag' [2025-06-27T05:06:52.130Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/functional/MBCS_Tests' [2025-06-27T05:06:52.130Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/functional' [2025-06-27T05:06:52.130Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests' [2025-06-27T05:06:52.130Z] [2025-06-27T05:06:52.130Z] [2025-06-27T05:06:52.130Z] All tests finished, run result summary: [2025-06-27T05:06:52.130Z] cd "/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-06-27T05:06:52.130Z] perl "resultsSum.pl" --failuremk="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/TKG/../TKG/failedtargets.mk" --resultFile="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/TKG/../TKG/output_17510006953143/TestTargetResult" --platFile="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/TKG/../TKG/resources/buildPlatformMap.properties" --diagnostic=failure --jdkVersion=25 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=linux_390-64 --buildList=functional --customTarget="" --testTarget=special.functional --tapPath=/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/TKG/../TKG/output_17510006953143/ --tapName=Test_openjdk25_hs_special.functional_s390x_linux.tap --comment="" [2025-06-27T05:06:52.330Z] [2025-06-27T05:06:52.330Z] [2025-06-27T05:06:52.330Z] TEST TARGETS SUMMARY [2025-06-27T05:06:52.330Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-27T05:06:52.330Z] DISABLED test targets: [2025-06-27T05:06:52.330Z] MBCS_Tests_locale_matching_zh_CN_aix_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_locale_matching_Zh_CN_aix_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_formatter_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_formatter_Zh_TW_aix_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_formatter_zh_TW_aix_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_formatter_ZH_TW_aix_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_formatter_tw_windows_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_i18n_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_i18n_ko_KR_aix_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_i18n_KO_KR_aix_0 [2025-06-27T05:06:52.330Z] [2025-06-27T05:06:52.330Z] PASSED test targets: [2025-06-27T05:06:52.330Z] MBCS_Tests_jdbc41_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_jdbc41_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_jdbc41_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_jdbc41_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_Compiler_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_Compiler_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_Compiler_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_Compiler_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_codepoint_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_sealed_classes_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_sealed_classes_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_sealed_classes_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_sealed_classes_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_coin_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_coin_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_coin_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_coin_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_datetime_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_datetime_formatter_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_locale_matching_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_locale_matching_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_locale_matching_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_locale_matching_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_switch_expressions_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_switch_expressions_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_switch_expressions_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_switch_expressions_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_text_blocks_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_text_blocks_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_text_blocks_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_text_blocks_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_urlclassloader_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_urlclassloader_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_urlclassloader_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_urlclassloader_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_pattern_matching_instanceof_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_pattern_matching_instanceof_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_pattern_matching_instanceof_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_pattern_matching_instanceof_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_scanner_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_scanner_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_scanner_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_scanner_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_StAX_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_StAX_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_StAX_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_StAX_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_codepage_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_codepage_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_codepage_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_codepage_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_compact_number_format_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_compact_number_format_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_compact_number_format_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_compact_number_format_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_record_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_record_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_record_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_record_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_IDN_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_IDN_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_IDN_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_IDN_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_file_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_file_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_file_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_file_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_charsets_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_formatter_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_formatter_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_formatter_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_nio_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_nio_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_nio_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_nio_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_env_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_env_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_env_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_env_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_unicode_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_regex_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_regex_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_regex_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_regex_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_new_jp_era_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_i18n_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_i18n_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_i18n_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_pref_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_pref_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_pref_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_pref_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_jaxp14_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_jaxp14_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_jaxp14_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_jaxp14_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_property_utf8_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_annotation_ja_JP_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_annotation_ko_KR_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_annotation_zh_CN_linux_0 [2025-06-27T05:06:52.330Z] MBCS_Tests_annotation_zh_TW_linux_0 [2025-06-27T05:06:52.330Z] [2025-06-27T05:06:52.330Z] FAILED test targets: [2025-06-27T05:06:52.330Z] MBCS_Tests_language_tag_0 [2025-06-27T05:06:52.330Z] [2025-06-27T05:06:52.330Z] TOTAL: 452 EXECUTED: 102 PASSED: 101 FAILED: 1 DISABLED: 10 SKIPPED: 340 [2025-06-27T05:06:52.330Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-27T05:06:52.330Z] [2025-06-27T05:06:52.330Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-27T05:06:52.330Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux/aqa-tests/TKG' [2025-06-27T05:06:52.330Z] make: *** [makefile:66: _special.functional] Error 2 [Pipeline] sh [2025-06-27T05:06:53.681Z] ++ uname [2025-06-27T05:06:53.681Z] + '[' Linux = AIX ']' [2025-06-27T05:06:53.681Z] ++ uname [2025-06-27T05:06:53.681Z] + '[' Linux = SunOS ']' [2025-06-27T05:06:53.681Z] ++ uname [2025-06-27T05:06:53.681Z] + '[' Linux = '*BSD' ']' [2025-06-27T05:06:53.681Z] + MAKE=make [2025-06-27T05:06:53.681Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-27T05:06:53.681Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-27T05:06:53.969Z] $ ssh-agent -k [2025-06-27T05:06:53.990Z] unset SSH_AUTH_SOCK; [2025-06-27T05:06:53.990Z] unset SSH_AGENT_PID; [2025-06-27T05:06:53.990Z] echo Agent pid 2693292 killed; [2025-06-27T05:06:54.479Z] [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] } [2025-06-27T05:06:54.515Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-06-27T05:06:54.962Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-27T05:06:55.182Z] TAP Reports Processing: START [2025-06-27T05:06:55.183Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-27T05:06:55.306Z] Saving reports... [2025-06-27T05:06:55.610Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_s390x_linux/builds/19/tap-master-files/aqa-tests/TKG/output_17510006953143/Test_openjdk25_hs_special.functional_s390x_linux.tap' [2025-06-27T05:06:55.611Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_s390x_linux/builds/19/tap-master-files/aqa-tests/TKG/output_17510006953143/Test_openjdk25_hs_special.functional_s390x_linux.tap]. [2025-06-27T05:06:55.636Z] There are failed test cases. Marking build as UNSTABLE [2025-06-27T05:06:55.636Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-27T05:06:55.645Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T05:06:55.762Z] Archiving artifacts [2025-06-27T05:06:56.004Z] Recording fingerprints [Pipeline] echo [2025-06-27T05:06:56.122Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T05:06:56.236Z] Archiving artifacts [2025-06-27T05:06:56.482Z] Recording fingerprints [Pipeline] sh [2025-06-27T05:06:57.856Z] + tar -cf - ./aqa-tests/TKG/output_17510006953143 [2025-06-27T05:06:57.856Z] + pigz -9 [2025-06-27T05:06:57.856Z] + gzip -9 [Pipeline] echo [2025-06-27T05:06:58.103Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-27T05:06:58.223Z] Archiving artifacts [2025-06-27T05:06:58.531Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-27T05:06:59.366Z] Tap file found: aqa-tests/TKG/output_17510006953143/Test_openjdk25_hs_special.functional_s390x_linux.tap... [Pipeline] readFile [Pipeline] echo [2025-06-27T05:07:00.026Z] 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=s390x_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%2Fjdk25%2Fjdk25-linux-s390x-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk-25%2B29_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=3&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-27T05:07:00.155Z] Recording test results [2025-06-27T05:07:00.985Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-27T05:07:01.057Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-27T05:07:02.394Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-06-27T05:07:02.394Z] Unix type machine.. [2025-06-27T05:07:02.394Z] Running on a Linux host [2025-06-27T05:07:02.394Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-27T05:07:02.829Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T05:07:02.829Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T05:07:04.485Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-27T05:07:05.825Z] + find /tmp -name '*core*' -print -exec rm -f '{}' ';' [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-27T05:07:06.119Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-27T05:07:06.481Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-27T05:07:06.642Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-27T05:07:06.863Z] Running on test-docker-fedora39-armv8l-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux [Pipeline] { [Pipeline] cleanWs [2025-06-27T05:07:07.586Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T05:07:07.586Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T05:07:07.881Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-27T05:07:09.341Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T05:07:09.341Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T05:07:09.637Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-27T05:07:09.842Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-27T05:07:09.900Z] Running on test-osuosl-aix72-ppc64-3 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux [Pipeline] { [Pipeline] echo [2025-06-27T05:07:09.965Z] Generating rerun Test_openjdk25_hs_special.functional_s390x_linux_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.functional_s390x_linux_rerun) [Pipeline] echo [2025-06-27T05:07:10.052Z] GENERATE_JOBS is set to true, set test job Test_openjdk25_hs_special.functional_s390x_linux_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-06-27T05:07:12.328Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-27T05:07:13.764Z] Processing DSL script testJobTemplate [2025-06-27T05:12:03.365Z] LEVELS: [special] [2025-06-27T05:12:03.365Z] JDK_VERSIONS: [8] [2025-06-27T05:12:03.365Z] GROUPS: [functional] [2025-06-27T05:12:03.367Z] ARCH_OS_LIST: [s390x_linux] [2025-06-27T05:12:03.740Z] Existing items: [2025-06-27T05:12:03.740Z] GeneratedJob{name='Test_openjdk25_hs_special.functional_s390x_linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-27T05:12:05.302Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.functional_s390x_linux_rerun) [Pipeline] build [2025-06-27T05:12:05.342Z] Scheduling project: Test_openjdk25_hs_special.functional_s390x_linux_rerun [2025-06-27T05:12:14.001Z] Starting building: Test_openjdk25_hs_special.functional_s390x_linux_rerun #19 [2025-06-27T11:43:03.364Z] Build Test_openjdk25_hs_special.functional_s390x_linux_rerun #19 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-27T11:43:03.565Z] Running on test-docker-fedora39-ppc64le-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_s390x_linux [Pipeline] { [Pipeline] cleanWs [2025-06-27T11:43:03.963Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T11:43:03.964Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T11:43:04.145Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-27T11:43:04.159Z] Test_openjdk25_hs_special.functional_s390x_linux_rerun #19 completed with status UNSTABLE [Pipeline] timeout [2025-06-27T11:43:04.163Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-27T11:43:05.433Z] Copied 1 artifact from "Test_openjdk25_hs_special.functional_s390x_linux_rerun" build number 19 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-27T11:43:05.700Z] TAP Reports Processing: START [2025-06-27T11:43:05.701Z] Looking for TAP results report in workspace using pattern: Test_openjdk25_hs_special.functional_s390x_linux_rerun/19/**/*.tap [2025-06-27T11:43:05.878Z] Saving reports... [2025-06-27T11:43:06.235Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_s390x_linux/builds/19/tap-master-files/Test_openjdk25_hs_special.functional_s390x_linux_rerun/19/aqa-tests/TKG/output_17510245651307/Test_openjdk25_hs_special.functional_s390x_linux_rerun.tap' [2025-06-27T11:43:06.235Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_s390x_linux/builds/19/tap-master-files/Test_openjdk25_hs_special.functional_s390x_linux_rerun/19/aqa-tests/TKG/output_17510245651307/Test_openjdk25_hs_special.functional_s390x_linux_rerun.tap]. [2025-06-27T11:43:06.243Z] There are failed test cases. Marking build as UNSTABLE [2025-06-27T11:43:06.280Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-27T11:43:06.285Z] Saving Test_openjdk25_hs_special.functional_s390x_linux_rerun/19/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-27T11:43:06.466Z] Archiving artifacts [2025-06-27T11:43:06.832Z] 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-06-27T11:43:08.436Z] [WS-CLEANUP] Deleting project workspace... [2025-06-27T11:43:08.436Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-27T11:43:08.613Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE