HeartSaVioR opened a new pull request, #57739: URL: https://github.com/apache/spark/pull/57739
### What changes were proposed in this pull request? The scheduled Maven workflows on `branch-4.x` were building `master`, not the branch. They call the reusable `maven_test.yml` without passing a `branch` input, and that workflow declared `default: master`, which it then uses as the checkout ref. Five workflows on this branch rely on the default: `build_maven.yml`, `build_maven_java21.yml`, `build_maven_java25.yml`, `build_maven_java21_arm.yml` and `build_maven_java21_macos26.yml`. Point the default at `branch-4.x`, matching `build_and_test.yml` on this branch (already `branch-4.x`) and both reusable workflows on `branch-4.2` and `branch-4.1` (each defaulting to their own branch, which is why their callers correctly pass no input). Also retitle `build_maven_java21_arm.yml` and `build_maven_java21_macos26.yml`, which still said `master` in their names — a stale artifact of being copied from `master` (the same two are stale on `branch-4.2`). They ran against `master` only because of the default this commit fixes, so the names would otherwise become actively wrong. Callers that target another branch pass `branch:` explicitly (e.g. `build_branch41_maven.yml` passes `branch-4.1`) and are unaffected. This misreporting masked SPARK-57897, where `branch-4.x` could not load its Maven project model at all, yet the branch's Maven workflow kept reporting success. ### Why are the changes needed? branch-4.x refers to master branch on CI which ended up with missing Maven build failure. ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? N/A ### Was this patch authored or co-authored using generative AI tooling? Generated-by: 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
