SEPURI-SAI-KRISHNA commented on issue #12612: URL: https://github.com/apache/seatunnel/issues/12612#issuecomment-6437201065
Reporting the rerun as promised, @SEZ9, rather than leaving it implied. **#12899 Build is green on `639908b12`**, the head carrying the documentation changes, so the red badge I warned you about is gone. The lane that had failed passed on both JDKs: | job | result | duration | | --- | --- | --- | | `all-connectors-it-3` (11) | success | 114m46s | | `all-connectors-it-3` (17) | success | 147m48s | No other job in the run is anything but success or skipped. **One thing I would rather flag than let you discover later.** The JDK 17 lane finished in 147m48s against a 150 minute cap, so it cleared by 2m12s. The previous attempt did not fail for an interesting reason: it hit that cap at exactly 150m on both JDKs. So this is not a flake that has now gone away, it is a lane running close enough to its limit that a slower runner tips it over. The same lane took 112m on `275efb97b` one commit earlier, which is the variance in question. That matters for you only in one way: if you see this PR go red again on `all-connectors-it-3` with no test failure named, it is the cap rather than the change, and a rerun is the right response. Nothing about it points at the `BIGINT` range check, which touches no connector code. So from my side #12899 now has a green Build on the reviewed head, no conflicts against current `dev`, and the documentation changes you asked for. The only remaining gate is the write-access review. -- 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]
