See <https://ci-builds.apache.org/job/POI/job/POI-DSL-IBM-JDK/331/display/redirect?page=changes>
Changes: [github] Bump actions/setup-java from 5 to 6 (#1225) [github] Fix two OPC part-name handling issues (percent-escape bounds check, [github] Remove dead SchemaFactory-hardening code from XSSFExportToXml (#1229) [github] Bump github/codeql-action from 4.37.8 to 4.37.9 (#1226) [github] Avoid large eager allocation from untrusted zip entry size in [github] Apply DEFAULT_XML_OPTIONS to remaining XMLBeans parses in xslf/xdgf [github] Escape relationship id interpolated into drawing fragment in [github] Fix Biff8DecryptingStream.readFully to honour len on the never-encrypted [github] Restrict OOXML signature reference dereferencing to the package (#1233) [github] Restore sized reads for known zip entry sizes while capping the initial [PJ Fanning] Buffer large/unknown-size zip entries to temp files in poi-integration [github] Spill unknown-size zip entries to temp files only once they exceed the [github] Fix `findColumnIndex()` to handle newline characters in column headers [PJ Fanning] Cap poi-integration test parallelism and raise heap on CI [github] Use more Java 17 idioms in poi-ooxml (#1237) [github] Use more Java 17 idioms in poi-scratchpad (#1238) [github] Use more Java 17 idioms in the poi core module (#1239) [github] Fix ContentType.equals and the M1.10 part name segment check (#1240) [github] Cache the TransformerFactory and skip unwanted comment lookups (#1241) [github] Avoid quadratic XmlBeans element access on hot paths (#1242) [github] Reduce the per-run work done when opening a Word document (#1243) [github] Avoid building XmlBeans objects for every shared string (#1244) [github] Fix off-by-one when stripping the [] wrapper from an external book name [github] try xmlbeans 5.4.1-RC0 version ------------------------------------------ [...truncated 775.73 KiB...] [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 12, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.988000 sec [junitlauncher] Sep 06, 2026 7:36:44 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] Running org.apache.poi.ooxml.TestPOIXMLProperties [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] [junitlauncher] Running org.apache.poi.ooxml.TestPOIXMLProperties [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:36:44 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] Tests run: 14, Failures: 0, Aborted: 0, Skipped: 1, Time elapsed: 0.667000 sec [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] Running org.apache.poi.ooxml.TestTriggerCoverage [junitlauncher] [junitlauncher] [junitlauncher] Running org.apache.poi.ooxml.TestTriggerCoverage [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Aborted: [12] <https://ci-builds.apache.org/job/POI/job/POI-DSL-IBM-JDK/ws/test-data/integration/stress025.docx>: org.opentest4j.TestAbortedException: Assumption failed: File <https://ci-builds.apache.org/job/POI/job/POI-DSL-IBM-JDK/ws/test-data/integration/stress025.docx> is expected to fail [junitlauncher] Sep 06, 2026 7:37:06 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] Tests run: 29, Failures: 0, Aborted: 1, Skipped: 1, Time elapsed: 21.158000 sec [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Running org.apache.poi.ooxml.TestXMLPropertiesTextExtractor [junitlauncher] [junitlauncher] Running org.apache.poi.ooxml.TestXMLPropertiesTextExtractor [junitlauncher] Sep 06, 2026 7:37:06 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] Tests run: 6, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.127000 sec [junitlauncher] Running org.apache.poi.openxml4j.TestOPCPackage [junitlauncher] [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.TestOPCPackage [junitlauncher] Tests run: 3, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.010000 sec [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:06 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Running org.apache.poi.openxml4j.TestOPCPackageFileLimit [junitlauncher] Sep 06, 2026 7:37:06 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.TestOPCPackageFileLimit [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] Tests run: 2, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.005000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.TestContentType [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Running org.apache.poi.openxml4j.opc.TestContentType [junitlauncher] Tests run: 45, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.078000 sec [junitlauncher] Sep 06, 2026 7:37:06 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestEncryptedTempFilePackagePart [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestEncryptedTempFilePackagePart [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:06 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.176000 sec [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] Running org.apache.poi.openxml4j.opc.TestFileHelper [junitlauncher] [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestFileHelper [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.002000 sec [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Running org.apache.poi.openxml4j.opc.TestListParts [junitlauncher] Sep 06, 2026 7:37:06 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] Running org.apache.poi.openxml4j.opc.TestListParts [junitlauncher] [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.005000 sec [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:06 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackage [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackage [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] Tests run: 45, Failures: 0, Aborted: 0, Skipped: 1, Time elapsed: 1.819000 sec [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackageCoreProperties [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackageCoreProperties [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 7, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.076000 sec [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackagePartCollection [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackagePartCollection [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.005000 sec [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackagePartName [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackagePartName [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.001000 sec [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackageThumbnail [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackageThumbnail [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.018000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackagingURIHelper [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestPackagingURIHelper [junitlauncher] Tests run: 5, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.006000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.TestRelationships [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestRelationships [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 9, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.075000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.TestStreamHelper [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestStreamHelper [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 3, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.059000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.TestTempFilePackagePart [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.TestTempFilePackagePart [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.006000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.compliance.TestOPCComplianceCoreProperties [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.compliance.TestOPCComplianceCoreProperties [junitlauncher] Sep 06, 2026 7:37:08 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 15, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.118000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.compliance.TestOPCCompliancePackageModel [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.compliance.TestOPCCompliancePackageModel [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 8, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.052000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.compliance.TestOPCCompliancePartName [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.compliance.TestOPCCompliancePartName [junitlauncher] Tests run: 10, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.010000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.internal.TestContentTypeManager [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.internal.TestContentTypeManager [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 4, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.137000 sec [junitlauncher] Running org.apache.poi.openxml4j.opc.internal.marshallers.TestZipPackagePropertiesMarshaller [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.opc.internal.marshallers.TestZipPackagePropertiesMarshaller [junitlauncher] Tests run: 3, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.005000 sec [junitlauncher] Running org.apache.poi.openxml4j.util.TestXSSFWorkbookWithMemoryConfigs [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.util.TestXSSFWorkbookWithMemoryConfigs [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.012000 sec [junitlauncher] Running org.apache.poi.openxml4j.util.TestZipArchiveFakeEntry [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.util.TestZipArchiveFakeEntry [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 10, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.019000 sec [junitlauncher] Running org.apache.poi.openxml4j.util.TestZipSecureFile [junitlauncher] [junitlauncher] Running org.apache.poi.openxml4j.util.TestZipSecureFile [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] Tests run: 12, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.213000 sec [junitlauncher] Running org.apache.poi.poifs.crypt.dsig.TestNecessaryClasses [junitlauncher] [junitlauncher] Running org.apache.poi.poifs.crypt.dsig.TestNecessaryClasses [junitlauncher] Tests run: 1, Failures: 0, Aborted: 0, Skipped: 0, Time elapsed: 0.018000 sec [junitlauncher] Running org.apache.poi.poifs.crypt.dsig.TestOOXMLURIDereferencer [junitlauncher] Sep 06, 2026 7:37:09 AM org.junit.platform.launcher.core.DiscoveryIssueNotifier logIssues [junitlauncher] INFO: TestEngine with ID 'junit-jupiter' encountered a non-critical issue during test discovery: [junitlauncher] [junitlauncher] (1) [INFO] Parallel test execution is enabled but the default ForkJoinPool-based executor service will be used. Please give the new implementation based on a regular thread pool a try by setting the 'junit.jupiter.execution.parallel.config.executor-service' configuration parameter to 'WORKER_THREAD_POOL' and report any issues to the JUnit team. Alternatively, set the configuration parameter to 'FORK_JOIN_POOL' to hide this message and keep using the original implementation. [junitlauncher] [junitlauncher] Running org.apache.poi.poifs.crypt.dsig.TestOOXMLURIDereferencer [junitlauncher] Failed: absoluteUriIsNotResolved(): javax.xml.crypto.NoSuchMechanismException: Mechanism DOM not available [junitlauncher] Tests run: 1, Failures: 1, Aborted: 0, Skipped: 0, Time elapsed: 0.018000 sec BUILD FAILED <https://ci-builds.apache.org/job/POI/job/POI-DSL-IBM-JDK/ws/build.xml>:1806: The following error occurred while executing this line: <https://ci-builds.apache.org/job/POI/job/POI-DSL-IBM-JDK/ws/build.xml>:1778: The following error occurred while executing this line: <https://ci-builds.apache.org/job/POI/job/POI-DSL-IBM-JDK/ws/build.xml>:1388: Some test(s) have failure(s) Total time: 8 minutes 29 seconds Build step 'Invoke Ant' marked build as failure [SpotBugs] Skipping execution of recorder since overall result is 'FAILURE' ERROR: Not all environment variables could be successfully injected. Check for similarly-named environment variables. Archiving artifacts ERROR: Not all environment variables could be successfully injected. Check for similarly-named environment variables. Recording test results ERROR: Not all environment variables could be successfully injected. Check for similarly-named environment variables. [Checks API] No suitable checks publisher found. ERROR: Not all environment variables could be successfully injected. Check for similarly-named environment variables. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
