Guosmilesmile opened a new pull request, #3692: URL: https://github.com/apache/fluss/pull/3692
## Description ### Problem The `lake` stage in CI (defined in `ci-template.yaml`) ran 6 sub-modules sequentially in a single Maven command: | Sub-module | Duration | |---|---| | fluss-lake (parent) | ~0 min | | fluss-lake-paimon | ~5 min | | fluss-lake-iceberg | ~5 min | | fluss-lake-lance | ~1 min | | fluss-flink-1.19 | ~24 min | | fluss-flink-1.18 | ~23 min | | **Total** | **~60 min** | This consistently triggered the step-level `timeout-minutes: 60` limit, causing the job to fail with: ``` Error: The action 'Test' has timed out after 60 minutes. ``` ### Solution Split the `lake` stage into two independent jobs that run in parallel via the GitHub Actions matrix: - **`lake`**: fluss-lake, fluss-lake-paimon, fluss-lake-iceberg, fluss-lake-lance (~12 min) - **`flink-backward`**: fluss-flink-1.19, fluss-flink-1.18 (~47 min) Since both jobs run in parallel (`fail-fast: false`), the wall-clock time drops from ~60 min to ~47 min, well within the timeout. ### Changes - `stage.sh`: Added `STAGE_FLINK_BACKWARD` / `MODULES_FLINK_BACKWARD`, split Flink 1.18/1.19 out of `MODULES_LAKE`, updated `get_test_modules_for_stage()` with new case and updated `core` negation. - `ci-template.yaml`: Added `flink-backward` to the matrix. -- 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]
