DanielLeens commented on PR #12755:
URL: https://github.com/apache/seatunnel/pull/12755#issuecomment-6397833843

   Thanks for the contribution. The remaining CI now has a concrete upstream 
fix; my earlier failed-job retry guidance should be updated. The current 
[Build](https://github.com/apache/seatunnel/runs/120252905531) is still failed 
for unchanged head `4c3f68db66eafc7f1366a92ec59f5692cf8eedca`. I retrieved the 
[HBase Java 17 
log](https://github.com/WXPNG/seatunnel/actions/runs/39770755603/job/120212249410):
 22 errors report `PreconditionViolationException: None of the supporting 
TestTemplateInvocationContextProviders ... provided a non-empty stream`.
   
   Latest dev contains 
[#12895](https://github.com/apache/seatunnel/pull/12895), commit 
`b65fe82b040c203ce669db83431916108f3e866e`, absent from this head. It adds a 
container-selection condition to skip suites/methods when every selected engine 
is explicitly disabled; genuine empty container discovery remains an error. 
This PR does not change that framework.
   
   Please **sync latest dev and rerun the affected failed jobs first**, rather 
than copying unrelated framework patches here or only retrying the old head. I 
inspected the HBase sample and the returned job page, not every failed matrix 
log; check the refreshed run for any distinct remaining failures. Correctly 
skipped unsupported engines are not runtime passes. My previous source-level 
conclusion remains clear; current-head CI and write-capable maintainer approval 
remain gates.
   
   Live comparison recorded in this batch: base dev, `diverged`, ahead 2 / 
behind 25. Daniel has READ permission; this is a technical follow-up, not an 
effective approval. No second source review is being issued on the unchanged 
head.
   


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