You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by ka...@apache.org on 2026/08/04 11:59:46 UTC
(spark) branch branch-4.x updated: [SPARK-58537][4.X][INFRA] Make maven_test.yml default to branch-4.x on branch-4.x
This is an automated email from the ASF dual-hosted git repository.
HeartSaVioR pushed a commit to branch branch-4.x
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/branch-4.x by this push:
new 12945792218e [SPARK-58537][4.X][INFRA] Make maven_test.yml default to branch-4.x on branch-4.x
12945792218e is described below
commit 12945792218e4417af700f840aa1bd670e8d7545
Author: Jungtaek Lim <ka...@gmail.com>
AuthorDate: Tue Aug 4 20:59:24 2026 +0900
[SPARK-58537][4.X][INFRA] Make maven_test.yml default to branch-4.x on branch-4.x
### 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?
scheduled CI will confirm with it.
### Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Opus 5
Closes #57739 from HeartSaVioR/fix-branch4x-maven-branch.
Authored-by: Jungtaek Lim <ka...@gmail.com>
Signed-off-by: Jungtaek Lim <ka...@gmail.com>
---
.github/workflows/build_maven_java21_arm.yml | 2 +-
.github/workflows/build_maven_java21_macos26.yml | 2 +-
.github/workflows/maven_test.yml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/.github/workflows/build_maven_java21_arm.yml b/.github/workflows/build_maven_java21_arm.yml
index 16417bb1c5f2..b8b55a737120 100644
--- a/.github/workflows/build_maven_java21_arm.yml
+++ b/.github/workflows/build_maven_java21_arm.yml
@@ -17,7 +17,7 @@
# under the License.
#
-name: "Build / Maven (master, Scala 2.13, Hadoop 3, JDK 21, ARM)"
+name: "Build / Maven (branch-4.x, Scala 2.13, Hadoop 3, JDK 21, ARM)"
on:
schedule:
diff --git a/.github/workflows/build_maven_java21_macos26.yml b/.github/workflows/build_maven_java21_macos26.yml
index c858a7f70b27..d4ba178dca16 100644
--- a/.github/workflows/build_maven_java21_macos26.yml
+++ b/.github/workflows/build_maven_java21_macos26.yml
@@ -17,7 +17,7 @@
# under the License.
#
-name: "Build / Maven (master, Scala 2.13, Hadoop 3, JDK 21, MacOS-26)"
+name: "Build / Maven (branch-4.x, Scala 2.13, Hadoop 3, JDK 21, MacOS-26)"
on:
schedule:
diff --git a/.github/workflows/maven_test.yml b/.github/workflows/maven_test.yml
index a857cf048953..fa7cdd20d6ba 100644
--- a/.github/workflows/maven_test.yml
+++ b/.github/workflows/maven_test.yml
@@ -30,7 +30,7 @@ on:
description: Branch to run the build against
required: false
type: string
- default: master
+ default: branch-4.x
hadoop:
description: Hadoop version to run with. HADOOP_PROFILE environment variable should accept it.
required: false
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org