kz930 opened a new issue, #7262: URL: https://github.com/apache/texera/issues/7262
### What happened? A PR whose title starts with `fix` is auto-labelled `release/v1.2` by `backport-auto-label.yml`. That is deliberate — `release-branches.yml` says backports should be opt-out rather than opt-in. The label starts the preflight in `backport-checks.yml`, which cherry-picks the change onto the release branch and builds it there using **main's** `build.yml`. That build step names its modules literally (`build.yml:308`): ``` sbt "DAO/jacoco" "Auth/jacoco" "Config/jacoco" "Resource/jacoco" "Util/jacoco" ... ``` `Resource` does not exist on `release/v1.2` — it was added to main on 2026-06-30 in `434bcae08`, after the branch was cut — so the step aborts with `No such setting/task: Resource/jacoco` and exits 1. The tests it reached had all passed (`Tests: succeeded 39, failed 0`). sbt stops at the first unknown name, so only `Resource` appears in the log. Reading `release/v1.2`'s own `build.sbt`, two more names in the same command are absent there too: `Util` and `WorkflowCompiler`. Ten module names are listed; seven resolve on that branch. Every `fix` PR currently open shows nine red `backport (release/v1.2) / …` jobs for this reason, whatever it changes. `backport-checks.yml`'s header states the preflight is "kept out of Required Checks so a conflicting backport is never a red X on the PR" — this failure is neither a cherry-pick conflict nor a real build break on the release branch, and it does show as a red X. Expected: the preflight builds the release branch with that branch's own module layout. Neither obvious one-line direction works — the names cannot be dropped from main's workflow, since those modules exist on main and their coverage is wanted there, and the modules should not be added to a released branch to satisfy CI. The list has to follow the branch being built. ### How to reproduce? 1. Open any PR to `main` with a title beginning `fix`. 2. `backport-auto-label.yml` adds the `release/v1.2` label and the preflight starts. 3. `backport (release/v1.2) / amber` fails with the error below, while the same job on `main` passes. ### Version/Branch 1.3.0-incubating-SNAPSHOT (main), preflight target `release/v1.2` ### Relevant log output ```shell [error] No such setting/task [error] Resource/jacoco [error] ^ ##[error]Process completed with exit code 1. ``` -- 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]
