[2025-06-12T22:30:22.506Z] make[5]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/functional/MBCS_Tests/urlclassloader' [2025-06-12T22:30:22.506Z] make[4]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/functional/MBCS_Tests' [2025-06-12T22:30:22.506Z] make[3]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/functional' [2025-06-12T22:30:22.506Z] make[2]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests' [2025-06-12T22:30:22.506Z] [2025-06-12T22:30:22.506Z] [2025-06-12T22:30:22.506Z] All tests finished, run result summary: [2025-06-12T22:30:22.506Z] cd "/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/TKG/../TKG/scripts"; \ [2025-06-12T22:30:22.506Z] perl "resultsSum.pl" --failuremk="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/TKG/../TKG/failedtargets.mk" --resultFile="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/TKG/../TKG/output_17497672468601/TestTargetResult" --platFile="/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/TKG/../TKG/resources/buildPlatformMap.properties" --diagnostic=failure --jdkVersion=25 --jdkImpl=hotspot --jdkVendor="eclipse" --spec=alpine-linux_aarch64 --buildList=functional --customTarget="" --testTarget=special.functional --tapPath=/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/TKG/../TKG/output_17497672468601/ --tapName=Test_openjdk25_hs_special.functional_aarch64_alpine-linux.tap --comment="" [2025-06-12T22:30:22.506Z] [2025-06-12T22:30:22.506Z] [2025-06-12T22:30:22.506Z] TEST TARGETS SUMMARY [2025-06-12T22:30:22.506Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-12T22:30:22.506Z] DISABLED test targets: [2025-06-12T22:30:22.506Z] MBCS_Tests_formatter_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_formatter_Zh_TW_aix_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_formatter_zh_TW_aix_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_formatter_ZH_TW_aix_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_formatter_tw_windows_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_i18n_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_i18n_ko_KR_aix_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_i18n_KO_KR_aix_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_locale_matching_zh_CN_aix_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_locale_matching_Zh_CN_aix_0 [2025-06-12T22:30:22.506Z] [2025-06-12T22:30:22.506Z] PASSED test targets: [2025-06-12T22:30:22.506Z] MBCS_Tests_Compiler_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_Compiler_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_Compiler_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_Compiler_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_IDN_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_IDN_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_IDN_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_IDN_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_StAX_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_StAX_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_StAX_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_StAX_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_annotation_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_annotation_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_annotation_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_annotation_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_charsets_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_codepage_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_codepage_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_codepage_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_codepage_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_codepoint_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_coin_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_coin_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_coin_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_coin_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_compact_number_format_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_compact_number_format_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_compact_number_format_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_compact_number_format_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_datetime_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_datetime_formatter_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_env_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_env_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_env_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_env_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_file_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_file_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_file_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_file_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_formatter_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_formatter_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_formatter_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_i18n_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_i18n_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_i18n_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_jaxp14_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_jaxp14_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_jaxp14_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_jaxp14_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_jdbc41_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_jdbc41_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_jdbc41_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_jdbc41_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_locale_matching_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_locale_matching_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_locale_matching_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_locale_matching_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_new_jp_era_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_nio_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_nio_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_nio_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_nio_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_pattern_matching_instanceof_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_pattern_matching_instanceof_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_pattern_matching_instanceof_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_pattern_matching_instanceof_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_pref_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_pref_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_pref_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_pref_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_property_utf8_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_record_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_record_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_record_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_record_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_regex_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_regex_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_regex_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_regex_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_scanner_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_scanner_ko_KR_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_scanner_zh_CN_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_scanner_zh_TW_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_sealed_classes_ja_JP_linux_0 [2025-06-12T22:30:22.506Z] MBCS_Tests_sealed_classes_ko_KR_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_sealed_classes_zh_CN_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_sealed_classes_zh_TW_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_switch_expressions_ja_JP_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_switch_expressions_ko_KR_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_switch_expressions_zh_CN_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_switch_expressions_zh_TW_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_text_blocks_ja_JP_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_text_blocks_ko_KR_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_text_blocks_zh_CN_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_text_blocks_zh_TW_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_unicode_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_urlclassloader_ja_JP_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_urlclassloader_ko_KR_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_urlclassloader_zh_CN_linux_0 [2025-06-12T22:30:22.507Z] MBCS_Tests_urlclassloader_zh_TW_linux_0 [2025-06-12T22:30:22.507Z] [2025-06-12T22:30:22.507Z] FAILED test targets: [2025-06-12T22:30:22.507Z] MBCS_Tests_language_tag_0 [2025-06-12T22:30:22.507Z] [2025-06-12T22:30:22.507Z] TOTAL: 452 EXECUTED: 102 PASSED: 101 FAILED: 1 DISABLED: 10 SKIPPED: 340 [2025-06-12T22:30:22.507Z] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ [2025-06-12T22:30:22.507Z] [2025-06-12T22:30:22.507Z] make[1]: *** [settings.mk:454: resultsSummary] Error 2 [2025-06-12T22:30:22.507Z] make[1]: Leaving directory '/home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/aqa-tests/TKG' [2025-06-12T22:30:22.507Z] make: *** [makefile:66: _special.functional] Error 2 [Pipeline] sh [2025-06-12T22:30:24.316Z] + uname [2025-06-12T22:30:24.316Z] + '[' Linux '=' AIX ] [2025-06-12T22:30:24.316Z] + uname [2025-06-12T22:30:24.316Z] + '[' Linux '=' SunOS ] [2025-06-12T22:30:24.316Z] + uname [2025-06-12T22:30:24.316Z] + '[' Linux '=' '*BSD' ] [2025-06-12T22:30:24.316Z] + MAKE=make [2025-06-12T22:30:24.316Z] + make -f ./aqa-tests/TKG/testEnv.mk testEnvTeardown [2025-06-12T22:30:24.316Z] make: Nothing to be done for 'testEnvTeardown'. [Pipeline] } [2025-06-12T22:30:24.701Z] Xvfb stopping [Pipeline] // wrap [Pipeline] echo [2025-06-12T22:30:25.173Z] There were test failures, set build result to UNSTABLE. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Post) [Pipeline] step [2025-06-12T22:30:25.391Z] TAP Reports Processing: START [2025-06-12T22:30:25.392Z] Looking for TAP results report in workspace using pattern: aqa-tests/TKG/**/*.tap [2025-06-12T22:30:25.539Z] Saving reports... [2025-06-12T22:30:25.926Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/builds/15/tap-master-files/aqa-tests/TKG/output_17497672468601/Test_openjdk25_hs_special.functional_aarch64_alpine-linux.tap' [2025-06-12T22:30:25.926Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/builds/15/tap-master-files/aqa-tests/TKG/output_17497672468601/Test_openjdk25_hs_special.functional_aarch64_alpine-linux.tap]. [2025-06-12T22:30:25.954Z] There are failed test cases. Marking build as UNSTABLE [2025-06-12T22:30:25.954Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-12T22:30:25.963Z] Saving aqa-tests/testenv/testenv.properties file on jenkins. [Pipeline] archiveArtifacts [2025-06-12T22:30:26.099Z] Archiving artifacts [2025-06-12T22:30:26.364Z] Recording fingerprints [Pipeline] echo [2025-06-12T22:30:26.511Z] Saving aqa-tests/TKG/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-12T22:30:26.648Z] Archiving artifacts [2025-06-12T22:30:26.967Z] Recording fingerprints [Pipeline] sh [2025-06-12T22:30:28.569Z] + tar -cf - ./aqa-tests/TKG/output_17497672468601 [2025-06-12T22:30:28.569Z] + pigz -9 [2025-06-12T22:30:28.569Z] + gzip -9 [Pipeline] echo [2025-06-12T22:30:28.958Z] ARTIFACTORY_SERVER is not set. Saving artifacts on jenkins. [Pipeline] archiveArtifacts [2025-06-12T22:30:29.097Z] Archiving artifacts [2025-06-12T22:30:29.490Z] Recording fingerprints [Pipeline] findFiles [Pipeline] echo [2025-06-12T22:30:31.170Z] Tap file found: aqa-tests/TKG/output_17497672468601/Test_openjdk25_hs_special.functional_aarch64_alpine-linux.tap... [Pipeline] readFile [Pipeline] echo [2025-06-12T22:30:31.849Z] 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=aarch64_alpine-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-alpine-linux-aarch64-temurin&OPENJ9_REPO=https%3A%2F%2Fgithub.com%2Feclipse-openj9%2Fopenj9.git&CLOUD_PROVIDER=&CUSTOM_TARGET=&VENDOR_TEST_SHAS=&JDK_BRANCH=jdk-25%2B27_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=199&STF_OWNER_BRANCH=adoptium%3Amaster&TIME_LIMIT=25&JVM_OPTIONS=&PARALLEL=None [Pipeline] junit [2025-06-12T22:30:32.067Z] Recording test results [2025-06-12T22:30:33.494Z] [Checks API] No suitable checks publisher found. [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-12T22:30:33.562Z] PROCESSCATCH: Terminating any hung/left over test processes: [Pipeline] sh [2025-06-12T22:30:35.019Z] + aqa-tests/terminateTestProcesses.sh jenkins [2025-06-12T22:30:35.019Z] Unix type machine.. [2025-06-12T22:30:35.019Z] Running on a Linux host [2025-06-12T22:30:35.019Z] Woohoo - no rogue processes detected! [Pipeline] cleanWs [2025-06-12T22:30:35.672Z] [WS-CLEANUP] Deleting project workspace... [2025-06-12T22:30:35.672Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-12T22:30:38.820Z] [WS-CLEANUP] done [Pipeline] sh [2025-06-12T22:30:40.410Z] + find /tmp -name '*core*' -print -exec rm -f '{}' ';' [Pipeline] } [Pipeline] // timeout [Pipeline] timeout [2025-06-12T22:30:41.660Z] Timeout set to expire in 5 min 0 sec [Pipeline] { [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] echo [2025-06-12T22:30:41.994Z] SETUP_LABEL: ci.role.test [Pipeline] stage [Pipeline] { (Parallel Tests) [Pipeline] parallel [2025-06-12T22:30:42.071Z] No branches to run [Pipeline] // parallel [Pipeline] node [2025-06-12T22:30:42.336Z] Running on test-docker-ubuntu1804-armv8l-4 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux [Pipeline] { [Pipeline] cleanWs [2025-06-12T22:30:42.651Z] [WS-CLEANUP] Deleting project workspace... [2025-06-12T22:30:42.651Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-12T22:30:42.781Z] [WS-CLEANUP] done [Pipeline] findFiles [Pipeline] cleanWs [2025-06-12T22:30:43.196Z] [WS-CLEANUP] Deleting project workspace... [2025-06-12T22:30:43.196Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-12T22:30:43.326Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Rerun) [Pipeline] echo [2025-06-12T22:30:43.557Z] allocate a node for generating rerun job ... [Pipeline] node [2025-06-12T22:30:43.616Z] Running on test-docker-ubuntu2404-armv7-6 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux [Pipeline] { [Pipeline] echo [2025-06-12T22:30:43.646Z] Generating rerun Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun job for running failed test(s) ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun) [Pipeline] echo [2025-06-12T22:30:43.748Z] GENERATE_JOBS is set to true, set test job Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun params for generating the job [Pipeline] fileExists [Pipeline] sh [2025-06-12T22:30:45.520Z] + curl -Os https://raw.githubusercontent.com/adoptium/aqa-tests/master/buildenv/jenkins/testJobTemplate [Pipeline] jobDsl [2025-06-12T22:30:46.573Z] Processing DSL script testJobTemplate [2025-06-12T22:34:16.230Z] LEVELS: [special] [2025-06-12T22:34:16.230Z] JDK_VERSIONS: [8] [2025-06-12T22:34:16.231Z] GROUPS: [functional] [2025-06-12T22:34:16.231Z] ARCH_OS_LIST: [aarch64_alpine-linux] [2025-06-12T22:34:16.457Z] Existing items: [2025-06-12T22:34:16.457Z] GeneratedJob{name='Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun'} [Pipeline] } [Pipeline] // parallel [Pipeline] } [Pipeline] // node [Pipeline] echo [2025-06-12T22:34:17.726Z] Triggering rerun jobs in parallel ... [Pipeline] parallel [Pipeline] { (Branch: Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun) [Pipeline] build [2025-06-12T22:34:17.767Z] Scheduling project: Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun [2025-06-12T22:34:27.134Z] Starting building: Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun #14 [2025-06-13T04:17:13.944Z] Build Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun #14 completed: UNSTABLE [Pipeline] } [Pipeline] // parallel [Pipeline] node [2025-06-13T04:17:14.200Z] Running on test-osuosl-ubuntu2404-ppc64le-1 in /home/jenkins/workspace/Test_openjdk25_hs_special.functional_aarch64_alpine-linux [Pipeline] { [Pipeline] cleanWs [2025-06-13T04:17:14.587Z] [WS-CLEANUP] Deleting project workspace... [2025-06-13T04:17:14.587Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-13T04:17:14.785Z] [WS-CLEANUP] done [Pipeline] echo [2025-06-13T04:17:14.791Z] Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun #14 completed with status UNSTABLE [Pipeline] timeout [2025-06-13T04:17:14.794Z] Timeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] copyArtifacts [2025-06-13T04:17:16.078Z] Copied 1 artifact from "Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun" build number 14 [Pipeline] } [Pipeline] // timeout [Pipeline] step [2025-06-13T04:17:16.349Z] TAP Reports Processing: START [2025-06-13T04:17:16.349Z] Looking for TAP results report in workspace using pattern: Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun/14/**/*.tap [2025-06-13T04:17:16.526Z] Saving reports... [2025-06-13T04:17:16.884Z] Processing '/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/builds/15/tap-master-files/Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun/14/aqa-tests/TKG/output_17497882149842/Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun.tap' [2025-06-13T04:17:16.884Z] Parsing TAP test result [/home/jenkins/.jenkins/jobs/Test_openjdk25_hs_special.functional_aarch64_alpine-linux/builds/15/tap-master-files/Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun/14/aqa-tests/TKG/output_17497882149842/Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun.tap]. [2025-06-13T04:17:16.890Z] There are failed test cases. Marking build as UNSTABLE [2025-06-13T04:17:16.921Z] TAP Reports Processing: FINISH [Pipeline] echo [2025-06-13T04:17:16.927Z] Saving Test_openjdk25_hs_special.functional_aarch64_alpine-linux_rerun/14/**/*.tap file on jenkins. [Pipeline] archiveArtifacts [2025-06-13T04:17:17.108Z] Archiving artifacts [2025-06-13T04:17:17.466Z] 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-13T04:17:19.124Z] [WS-CLEANUP] Deleting project workspace... [2025-06-13T04:17:19.124Z] [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [2025-06-13T04:17:19.300Z] [WS-CLEANUP] done [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] End of Pipeline Finished: UNSTABLE