aIbrahiim commented on issue #30513:
URL: https://github.com/apache/beam/issues/30513#issuecomment-5874855709

   > [@aIbrahiim](https://github.com/aIbrahiim): have you experimented on your 
idea in [#30513 
(comment)](https://github.com/apache/beam/issues/30513#issuecomment-5795669787)?
 `LeaderBoardIT.test_leader_board_it` is still flaky.
   
   @shunping yes I tried that approach in 
https://github.com/apache/beam/pull/40241
   
   What I did there:
   1. timeout_secs on both BigQuery matchers (poll instead of one-shot)
   2. wait on Pub/Sub publish futures before asserting
   
   On the PR PostCommit runs, LeaderBoardIT passed on 3.10 / 3.11 / 3.12, but 
we still saw at least one empty-checksum fail (e.g. 3.14), so it looks reduced, 
not fully gone
   
   I wasn’t able to dig further at the time because PostCommit was also hitting 
IAM permission issues (403 PermissionDenied on GCP APIs like Vertex AI / 
Recommendations AI, and earlier some Pub/Sub / BigQuery 403s), which made the 
suite red for unrelated reasons.
   
   I’ll retrigger PostCommit on that PR and check the latest results


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