LuciferYang commented on PR #49357: URL: https://github.com/apache/spark/pull/49357#issuecomment-2574298153
> After merging, MacOS CI is triggered here. > > * https://github.com/apache/spark/actions/runs/12636667017 The test case `Query with Trigger.AvailableNow should throw error when offset(s) in planned topic partitions got unavailable during subsequent batches` seems quite unstable. I checked back and found that a similar test case, `Query with Trigger.AvailableNow should throw error when topic partitions got unavailable during subsequent batches`, failed frequently about two weeks ago. These two test cases are executed consecutively, and the error messages when they fail appear to be similar. `Query with Trigger.AvailableNow should throw error when topic partitions got unavailable during subsequent batches`: - https://github.com/apache/spark/actions/runs/12448087908/job/34752303825 - https://github.com/apache/spark/actions/runs/12496178777/job/34867666952 - https://github.com/apache/spark/actions/runs/12520214986/job/34925552658 - https://github.com/apache/spark/actions/runs/12573970266/job/35047528654 - https://github.com/apache/spark/actions/runs/12563518255/job/35025494839  `Query with Trigger.AvailableNow should throw error when offset(s) in planned topic partitions got unavailable during subsequent batches` - https://github.com/apache/spark/actions/runs/12636667017/job/35222481592 Need to investigate further. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
