The GitHub Actions job "Required Checks" on texera.git/fix/7049-serialize-minio-test-suites has failed. Run started by GitHub user Yicong-Huang (triggered by Yicong-Huang).
Head commit for run: 6a532c6881c16785a0e83401e184ebc8c677c70e / Yicong-Huang <[email protected]> test(workflow-core): serialize MinIO-backed suites to de-flake S3 tests `S3StorageClientSpec` intermittently failed 4 tests in the `build / amber` CI job (scope `WorkflowCore / Test / test`). The four suites mixing `S3StorageTestBase` (`S3StorageClientSpec`, `LargeBinaryManagerSpec`, `LargeBinaryInputStreamSpec`, `LargeBinaryOutputStreamSpec`) share a JVM-wide `S3StorageClient.s3Client` and a single `StorageConfig.s3Endpoint` pointed at one shared MinIO container. ScalaTest's parallel suite distributor runs them concurrently within a single in-process test task, so they contend for that one container and intermittently time out. Mirror the FileService approach for testcontainer suites: give each MinIO suite its own forked JVM via `Test / testGrouping`. sbt runs forked groups one at a time (Tags.ForkedTestGroup limit), so these suites never overlap; every other workflow-core suite stays in a single in-process group and keeps running in parallel. Also bound the concurrent-upload burst in the >1000-objects test from 16 to 4 threads so a single suite no longer floods the container. Closes #7049 Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/30488689262 With regards, GitHub Actions via GitBox
