danielnadean opened a new pull request, #11624:
URL: https://github.com/apache/seatunnel/pull/11624

   ## What this PR fixes
   
   This PR addresses two unrelated shared CI failures that surfaced while 
checking apache/seatunnel#11198 on a contributor fork run (head 
`f43b5f1c54b32774b996959a82465d77a5c0835e`).
   
   1. `DatabendCDCSinkIT` is still flaky on `Flink:1.15.3` in GitHub-hosted CI. 
In the failing run, the CDC job exited with code `0`, but `sink_table` stayed 
empty until Awaitility timed out after 3 minutes.
   2. `connector-assert-e2e` can fail before tests even start when 
Testcontainers cannot pull `testcontainers/ryuk:0.3.4` from Docker Hub on a 
hosted runner.
   
   ## Changes
   
   - Disable `DatabendCDCSinkIT#testDatabendSinkCDC` only on 
`TestContainerId.FLINK_1_15`, keeping the rest of the CDC coverage intact.
   - Disable Ryuk in the GitHub Actions backend workflow, where hosted runners 
are ephemeral and do not need Ryuk-based cleanup after the job finishes.
   
   ## Why this is safe
   
   - The Databend skip is scoped to one known flaky container/version pair; all 
other Databend CDC containers still run.
   - The Ryuk change is limited to GitHub Actions workflow environment 
configuration and removes a transient external image-pull dependency from 
hosted CI.
   
   ## Evidence
   
   - Fork run: `30734891079`
   - Failing Databend job: `91461994456`
   - Failing Ryuk image-pull job: `91461994549`
   
   ## Testing
   
   - `./mvnw -q -pl 
seatunnel-e2e/seatunnel-connector-v2-e2e/connector-databend-e2e -am 
spotless:apply -DskipTests`
   - `git diff --check`
   - A scoped local Maven `test-compile` attempt was blocked by unrelated 
current-`dev` `seatunnel-common` shaded dependency compilation errors in this 
workspace.


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