bvolpato opened a new pull request, #39622: URL: https://github.com/apache/beam/pull/39622
`StorageApiSinkSchemaUpdateIT` currently runs all 32 parameterized cases serially inside one test class. Gradle already gives GCP integration tests four forks, but it can only distribute work between classes. This splits the matrix by `useInputSchema` into two concrete test classes backed by the same test implementation. Each class owns a separate BigQuery dataset, so parallel setup and cleanup cannot interfere. Early-rollout coverage includes both classes explicitly. No test cases, assertions, row counts, stream counts, schema triggers, polling intervals, or soak delays change. ## Timing model [Scheduled master run 30486556613](https://github.com/apache/beam/actions/runs/30486556613/job/90693583636) recorded all 32 schema-update cases passing in 81m49s. Grouping those measured cases by the new class boundary gives: | Execution unit | Historical test time | | --- | ---: | | Current single class | 81m49s | | Without input schema | 52m10s | | With input schema | 29m39s | | Expected split critical path | 52m10s | This predicts a 29m39s, or 36%, reduction for this critical shard when both classes receive existing Gradle workers. It does not increase `maxParallelForks` or add another workflow job. Two classes are intentional. The longest individual parameter took 49m11s, only 2m59s below the two-class estimate. Splitting all four parameters would therefore add more concurrent Storage Write API tests for little additional critical-path gain. ## Testing - `./gradlew :sdks:java:io:google-cloud-platform:compileTestJava -PdisableSpotlessCheck=true` - `./gradlew :sdks:java:io:google-cloud-platform:spotlessJavaCheck` - `integrationTest --test-dry-run`: 32 cases discovered across two classes, no base-class tests - `bigQueryEarlyRolloutIntegrationTest --test-dry-run`: same 32 cases discovered PR remains draft until live GCP CI validates resource isolation and measured wall time. ------------------------ - [ ] No existing issue to link. - [ ] No `CHANGES.md` entry; test scheduling only. - [x] Small contribution; ICLA not applicable. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
