SEPURI-SAI-KRISHNA commented on PR #12568: URL: https://github.com/apache/seatunnel/pull/12568#issuecomment-5971391379
Update on my previous comment, where I offered to open a CI issue and PR for the `Build website` timeout. That work already exists and is not needed from me: @goutamadwant filed #12613 and #12614 at 14:51Z, about 80 minutes before I posted. Their root cause is more complete than mine. I had the timeout and the `api` path filter; they identified what changed. `apache/seatunnel-website#546` added the 3.0.0 docs snapshot on 2026-09-29, taking the website to 22 released versions, each built in both locales. Measured locally on one machine with `dev` docs synced: 155.6 minutes for all 22 versions, 12.9 minutes for the current docs plus the 3.0.0 snapshot. #12613 also lists five affected PRs, and the cancelled job from this PR is one of its data points, alongside #12573, #12597, #12578 and #12605. So #12614 is the path to a green badge here, and this PR is one instance of a repository wide problem rather than anything specific to the diff. One practical detail for whenever #12614 merges, because it affects what to do next on this PR. `backend.yml` is a `workflow_call` workflow, invoked by `build_main.yml` on push, so the definition that runs is the copy on the PR branch rather than the one on `dev`. Re-running the existing jobs would therefore reuse this branch's current `backend.yml` and build all 22 versions again. To pick up the fix I need to merge `dev` into the branch and push, which gives a new head and a fresh run. That makes the choice from my last comment concrete: 1. Wait for #12614, then I merge `dev` into this branch and push. The website job should finish in roughly 13 minutes and the check should go green on its own. 2. Treat the current job level result as sufficient: 82 successful, 0 failed, with `MultiTableSinkWriterTest` green on all four unit-test legs. I am happy with either, and I would lean towards the first now that the fix is already up for review, since it costs only the time for #12614 to land and leaves a genuinely green check rather than an explained red one. Just let me know which you prefer. -- 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]
