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

   CI status on head `1e5493c9f8`: Build run 
[32970480584](https://github.com/nielifeng/seatunnel/actions/runs/32970480584) 
completed with **76 green jobs** and only 3 non-green, all classified as 
environment/flake, none caused by this PR's diff:
   
   - `all-connectors-it-5 (8)` — Maven Central `Connection reset` downloading 
`org.testcontainers:databend:pom:1.20.2` (dependency-download infra failure; 
build never reached the tests).
   - `all-connectors-it-7 (8)` — `CouchbaseIT` 2/7, the known 
container-bootstrap flake already on record in earlier rounds.
   - `jdbc-connectors-it-part-1 (8)` — cancelled at the `timeout-minutes: 120` 
ceiling while tests were still passing normally (last activity: 
`JdbcMysqlTimestampIT` at 1h59m); the same leg passed the previous run in 
1h50m, so this is runner-speed budget, not a hang.
   
   Everything that previously failed is now green: all four `unit-test` legs 
(the `IncrementalSourceReaderTest` NPE fix is confirmed), both `engine-v2-it` 
legs, and — most relevant to this PR — `mysql-cdc-connector-it` and 
`oracle-cdc-connector-it` on both JDKs.
   
   @nielifeng could you hit **"Re-run failed jobs"** on that run? I tried `gh 
run rerun 32970480584 --failed` and the job-level variant, but reruns on the 
fork's Actions need repository admin rights, which maintainer edit access does 
not grant. One click on your side retries exactly the 3 jobs above without 
re-running the 76 green ones. If a fresh full run is easier for you, that works 
too — it just costs a few more hours of CI.
   
   Once those 3 come back green, the only remaining items are the non-blocking 
follow-ups already dispositioned in [my earlier 
comment](https://github.com/apache/seatunnel/pull/11503#issuecomment-5425538451),
 and the PR will be ready for @SEZ9's full re-review pass.
   


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