DanielLeens commented on PR #12152: URL: https://github.com/apache/seatunnel/pull/12152#issuecomment-6210069879
Thanks for the update, @CryoThrust, and for digging into the annotations instead of stopping at the missing logs. That matches what I found on my side for run `37615433319`: all 11 failed jobs carry the same "repeatedly failed to be acquired (5 attempts)" message, so they are runner-acquisition failures rather than test results. One practical note so nobody waits on the wrong thing: the apache-side `Build` check for `de042f22b` is still `queued` and points to that same run, so as of now there is no green result for this head. If the fork's workflows are paused on the GitHub side, as you observed, a fresh push to this branch will most likely queue behind the same pause, so a sync would not help until the fork's Actions are re-enabled. Once they are, "Re-run failed jobs" on that run is still the smallest option; if it keeps sitting in the queue, merging the latest `dev` (the branch is a few dozen commits behind) to start a brand-new run is a reasonable fallback. Nothing changes on the source side: the code-side blocker list is still empty, and the double-rejection branch stays the agreed follow-up alongside #12342. If any job fails with a real test failure after the rerun, please paste the job and test name and I will help classify it. -- 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]
