SEPURI-SAI-KRISHNA commented on PR #12568: URL: https://github.com/apache/seatunnel/pull/12568#issuecomment-5970960765
Rerun done, @nzw921rx. Every test job is green, but the badge is still red for a reason a rerun cannot fix, so here is the evidence rather than another attempt. Run `36966371906` attempt 3 on unchanged head `314556b79`: **82 successful, 11 skipped, 0 failed**. The only non-success is `Build website`, and it has now been cancelled on all three attempts at the same point: | attempt | start | end | duration | | --- | --- | --- | --- | | 1 | 05:23:36Z | 06:53:52Z | 90m16s | | 2 | 17:59:44Z | 19:30:08Z | 90m24s | | 3 | 13:35:58Z | 15:06:15Z | 90m17s | That is the `timeout-minutes: 90` on the `document` job in `.github/workflows/backend.yml`. Three attempts landing within eight seconds of the same wall clock is a deterministic timeout, not a flake, so a fourth rerun will end the same way. It is close, though. In attempt 3 both locale builds actually compiled: ``` [success] [webpackbar] Client: Compiled successfully in 19.88m [success] [webpackbar] Server: Compiled successfully in 38.10m [success] [webpackbar] Client: Compiled successfully in 24.48m [success] [webpackbar] Server: Compiled successfully in 45.25m 15:05:07Z ##[error]The operation was canceled. 15:06:11Z ``` The job was killed 64 seconds after the last successful compile, during post-compile static generation. One more thing worth noting: `Build website` runs on this PR only because its condition is `needs.changes.outputs.api == 'true' || needs.changes.outputs.docs == 'true'`. This PR changes three Java files in `seatunnel-api` and zero files under `docs/`, so the full bilingual website build is triggered by the `api` path filter alone, with no documentation in the diff for it to validate. So I cannot get this check green by rerunning. How would you like to proceed? 1. Treat the job-level result as the green signal: 82 successful, 0 failed, with the `MultiTableSinkWriterTest` additions passing on all four unit-test legs. 2. I open a separate CI issue and PR to either raise the `document` timeout or drop `api` from its condition, and this PR waits for that to land. Happy to do the second either way, since it affects every `seatunnel-api` change, not just this one. -- 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]
