davidzollo commented on PR #12108:
URL: https://github.com/apache/seatunnel/pull/12108#issuecomment-6886270010

   ### Implementation Notes and Trade-offs
   
   Head: `55b3469fd199a0b81e7ed83cddef8a25d45349c6`
   
   The previous 
[Build](https://github.com/apache/seatunnel/actions/runs/35737065515/job/106776931401)
 stopped before running `MetalakeIT`: Maven Central returned HTTP 403 while the 
job tried to download the Maven wrapper. That run is outside GitHub's retry 
window. Rebasing onto current `dev` picks up the merged wrapper retry backoff 
(#12468); the original test change still raises only Gravitino's readiness 
timeout from 180 to 300 seconds, with its poll interval and success assertion 
unchanged.
   
   I rebased the single test change rather than adding a workaround to the test 
or replaying the obsolete Build. The rebased patch is byte-for-byte identical 
to the original. The old head is preserved locally, and the GitHub update is 
leased against that exact prior head.
   
   Scoped Spotless apply/check and `git diff --check` passed. Spotless used the 
checkout's formatting configuration and targeted `MetalakeIT.java` directly, 
because the regular Maven module model requires an unavailable local JDBC 
SNAPSHOT BOM.
   
   GitHub confirmed the updated head, the same one-file PR scope, and no merge 
conflict. The new 
[Build](https://github.com/apache/seatunnel/actions/runs/43655962840) was 
running at readback; the readiness test result is still pending.
   


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