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

   CI follow-up on unchanged head `52cf78d80f197f159a65d50eae46817db0a04a51`: 
the earlier "queued / no executed result" statement is stale. [Build 
41602572467](https://github.com/DanielLeens/seatunnel/actions/runs/41602572467) 
finished with failure. The failed lanes are:
   
   - [all-connectors-it-2, JDK 
17](https://github.com/DanielLeens/seatunnel/actions/runs/41602572467/job/126675268625):
 Maven Central returned HTTP 409 while resolving `spring-security-bom:5.7.5` 
through the Aerospike dependency tree; this is dependency retrieval, not a 
checkpoint-test assertion.
   - [all-connectors-it-5, JDK 
11](https://github.com/DanielLeens/seatunnel/actions/runs/41602572467/job/126675271183):
 `TiDBCDCIT.startUp` fails in `TiDBTestBase.initializeTidbTable:213` during 
initial database setup.
   - [kafka-connector-it, JDK 
17](https://github.com/DanielLeens/seatunnel/actions/runs/41602572467/job/126675271233):
 `KafkaFormatIT.testFormatCompatibleTombstoneCheck:526` times out in 
`assertCommittedOffsetReached:1049`.
   
   These do not exercise the new coordinator unit-test fixture. The 
corresponding TiDB/Kafka test files are unchanged between this head and current 
dev; no upstream fix for these failures was found in that comparison, so a sync 
alone is not a demonstrated solution. The next step is Re-run failed jobs on 
this completed run. Repeated TiDB readiness or Kafka offset failures should be 
investigated separately with the new job logs, rather than changing this 
regression test or unrelated dependencies. No new source blocker is raised 
here; current-head CI remains required, followed by independent maintainer 
approval because Daniel is the author.
   


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