DanielLeens commented on PR #11500: URL: https://github.com/apache/seatunnel/pull/11500#issuecomment-6377542891
Thanks @zhangshenghang, I checked the updated PR description against head `fe8b1b39c12`. The "E2E harness note" now states that the `ContainerTestingExtension` / `ContainerUtil` changes were reverted and that skip policy stays with #12895, and the file list matches that. So Issue 1 from my last review is closed. On the red `Build`: I looked at fork run 39940766596 for this head. Most of the failed lanes (`all-connectors-it-6`, `all-connectors-it-2`, `transform-v2-it-part-2`, `hbase-connector-it`, each on JDK 11 and 17) fail with `PreconditionViolationException: None of the supporting TestTemplateInvocationContextProviders ... provided a non-empty stream`, for example in `FlinkMetricsIT`, `TestSparkDateTimeTransformIT`, `IcebergSourceIT` and `HbaseIT`. That is the "zeta-only PR run leaves no enabled container" case that the reverted harness change used to mask. The PR diff no longer touches any e2e harness code or Zeta slot allocation for those suites, so I do not read these as caused by the slot default. This is my inference from the logs. I could not find a clear test failure for the `mysql-cdc-connector-it` lanes in the logs I read, so I would not call them related or unrelated yet. Suggested next step, keeping it cheap: once #12895 lands, update this branch from `dev` and let the checks run again. That should clear the harness-related lanes without re-adding anything to this PR. Please also rerun the `mysql-cdc-connector-it` jobs on their own if they stay red. My source-level view is unchanged: ready, with the green `Build` as the only open gate. -- 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]
