Dev-next-gen commented on PR #12327:
URL: https://github.com/apache/seatunnel/pull/12327#issuecomment-5690150039

   You called the 99-row ClickHouse failure a test-isolation flake before I 
could confirm it, and the re-run backs that up. On attempt 2 of the same fork 
run, at the same commit 1d4e981 with nothing changed in between, 
`updated-modules-integration-test-part-6 (8, ubuntu-latest)` is green: `Tests 
run: 140, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2,477.524 s - in 
org.apache.seatunnel.connectors.seatunnel.clickhouse.ClickhouseIT` 
([job](https://github.com/Dev-next-gen/seatunnel/actions/runs/34970053909/job/104515013222)).
   
   The two jobs still red on that re-run are the ones I had already linked as 
failing on dev. part-2 ends on `OpengaussCDCIT.testAddFieldWithRestore:476 ยป 
ConditionTimeout` 
([job](https://github.com/Dev-next-gen/seatunnel/actions/runs/34970053909/job/104515012602)),
 and `rocketmq-connector-it (11)` on the same `Tests run: 87, Failures: 14, 
Errors: 29` in `RocketMqIT` 
([job](https://github.com/Dev-next-gen/seatunnel/actions/runs/34970053909/job/104515013565));
 its JDK 8 twin passed this time. Nothing in a module this PR touches is 
failing any more.
   
   The Build check on this page still shows the first attempt, because 
re-running a workflow in apache/seatunnel needs write access and `gh api 
repos/apache/seatunnel -q .permissions` returns 
`{"admin":false,"maintain":false,"pull":true,"push":false,"triage":false}` for 
my account, so if a green check is wanted before merge it has to come from 
someone on the project side.
   
   Found by a defect-hunting pipeline I build and run 
([Dev-next-gen](https://github.com/Dev-next-gen)), using Claude Code with 
Anthropic's Claude Opus 5.
   


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