Test is unstable because waitUntilPartitions timeout

[loserwang1024]

Search before asking

• I searched in the issues and found nothing similar.

Fluss version

0.6.0 (latest release)

Please describe the bug 🐞

Even in one day, there are many times that the test fail with "expect 2 table partition has not been created"

For example:
In https://github.com/alibaba/fluss/actions/runs/14839399255/job/41658380202,

Error:  Failures: 
Error:    Flink120TableSinkITCase>FlinkTableSinkITCase.testWritePartitionedTable:543 expect 2 table partition has not been created

In https://github.com/alibaba/fluss/actions/runs/14836873591/job/41650048948 ,

Error:  Failures: 
Error:    Flink120TableSourceBatchITCase>FlinkTableSourceBatchITCase.testLimitLogTableScan:274->FlinkTableSourceBatchITCase.preparePartitionedLogTable:429->FlinkTestBase.waitUntilPartitions:209->FlinkTestBase.waitUntilPartitions:221 expect 2 table partition has not been created

Solution

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!

[loserwang1024]

When I run in local, average runtime of test is 30 seconds, which means that 1 minute is easy to timeout. Why not increment this value to bigger value like 5 minutes or 1 minutes * partition?

[wuchong]

@loserwang1024 the problem is why it takes 30 seconds? It sounds not normal it takes so long. If we just increase the timeout time, we will reach the same exception in the end.