DanielLeens commented on issue #11638: URL: https://github.com/apache/seatunnel/issues/11638#issuecomment-5173416698
Thanks for raising this. This reads like a reasonable E2E enhancement rather than a bug. The underlying problem is clear: several of the custom E2E images used in SeaTunnel testing are effectively amd64-only today, which makes local E2E work on Apple Silicon slower and less reliable because it falls back to emulation. That is a real contributor-experience gap, especially for connector and engine debugging. A good implementation path would be: 1. identify the commonly used `tyrantlucifer/*` E2E images that block local ARM64 runs most often; 2. publish ARM64 or multi-arch variants for those images first; 3. keep image selection explicit in the tests/build scripts, following the existing architecture-based selection pattern where available; 4. document which E2E suites become natively runnable on Apple Silicon and which still depend on amd64-only upstream images. I've labeled this as `feature` and `help wanted` so contributors can pick it up. If someone works on it, the most useful first slice would be the highest-usage images plus one focused end-to-end verification showing native `linux/arm64` execution on Apple Silicon. -- 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]
