luoyuxia opened a new issue, #3273:
URL: https://github.com/apache/fluss/issues/3273

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and 
found nothing similar.
   
   ### Description
   
   Our current CI pipeline is spending too much time on Flink multi-version 
tests. In the linked run below, the longest CI job took more than 50 minutes, 
which is already very close to the current 60-minute timeout configured in CI:
   
   
https://github.com/apache/fluss/actions/runs/25545481655/job/74980566947?pr=3229
   
   The main bottleneck is the Flink multi-version test stage. At the moment, we 
run a broad set of Flink read/write tests across multiple Flink versions. This 
gives us coverage, but it also introduces a large amount of duplicated 
execution time.
   
   In practice, we do not need to run the full read/write test set on every 
supported Flink version. For compatibility validation, it should be enough to:
   
   - keep the full test suite on one primary Flink version;
   - keep only a small set of representative end-to-end read/write smoke tests 
on the remaining supported Flink versions;
   - retain dedicated tests only where a version-specific behavior actually 
needs coverage.
   
   This would still protect the core compatibility path while significantly 
reducing duplicated test time in CI. It should also reduce the risk of hitting 
the 60-minute timeout, especially as more tests are added later.
   
   A possible follow-up for this task is:
   
   - review the current Flink multi-version test matrix;
   - identify the minimal cross-version smoke coverage we really need;
   - move the rest of the read/write test coverage to a single representative 
version;
   - keep version-specific tests only when they validate behavior that is 
genuinely different across Flink versions.
   
   ### Willingness to contribute
   
   - [ ] I'm willing to submit a PR!
   


-- 
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]

Reply via email to