zhztheplayer commented on PR #13535: URL: https://github.com/apache/gluten/pull/13535#issuecomment-6823132302
> We could move ARM and Kafka first, see how the fork runs and the status sync work for a while, and then decide on x86. This also lets maintainers keep re-running flaky jobs on this core workflow. Does this make sense? Or should we also keep ARM workflow for now, and only move Kafka test to fork first? @philo-he just my 2 cents: I suggest we can just make the change all together. Per current discussion, this needs a verification after merging anyway; What about doing the following orderly: 1. Verify it in another repo like @LuciferYang suggests; 2. If all good, merge this PR (13535); 3. Open a new PR to verify, where the change can the moved workflows, expect the PR is blocked for merging, fix the issues respectively, expect the CI goes to green gradually; 4. If 3 fails, revert this PR (13535), fix, go to 1 again; the revert also requires at least 1 approver so make sure there's someone aware of this online proceeding. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
