You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@texera.apache.org by "mengw15 (via GitHub)" <gi...@apache.org> on 2026/09/21 21:15:56 UTC
[I] backport/ commit status is never updated after the backport lands [texera]
mengw15 opened a new issue, #8632:
URL: https://github.com/apache/texera/issues/8632
### What happened?
`direct-backport-push.yml` writes a `backport/<target>` commit status onto the squash commit on main, then nothing ever updates it — not when the backport PR merges, not when it is closed. The status records which code path ran at merge time, not whether the fix reached the branch, which is what it reads as.
Six landed backports still carry a red status on main today:
| source | backport | landed | status on main now |
| --- | --- | --- | --- |
| #8562 | #8585 | v1.2, 09-19 | `failure` — "Draft backport PR #8585 opened" |
| #7348 | #7530 | v1.2, 08-13 | `failure` — "Draft backport PR #7494 opened" |
| #7347 | #7529 | v1.2, 08-13 | `failure` — "Draft backport PR #7495 opened" |
| #7327 | #7518 | v1.2, 08-13 | `failure` — "Draft backport PR #7401 opened" |
| #7234 | #7306 | v1.2, 08-04 | `failure` — "Draft backport PR #7291 opened" |
| #8498 | #8500 | v1.3, 09-11 | `failure` — "Backport failed" |
The four middle rows also name a PR that was closed without merging — the one the first attempt opened — so the link goes to a dead PR.
### How to reproduce?
1. Merge a `fix:` PR whose backport conflicts, so a draft backport PR opens.
2. Finish and merge that backport PR.
3. `GET /repos/apache/texera/commits/<the source squash sha>/status` — `backport/<target>` is still `failure`.
**Fix**: a handler on the backport PR closing that resolves the source commit's status — success when merged, failure when closed unmerged. It belongs with the removal of the unreachable `push-backports` job, which holds the only `success` write for this context.
### Version/Branch
main
--
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: notifications-unsubscribe@texera.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] backport/ commit status is never updated after the backport lands [texera]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #8632:
URL: https://github.com/apache/texera/issues/8632#issuecomment-5767630680
<!-- texera:template-compliance -->
👋 Thanks for opening this issue, @mengw15!
It looks like the issue description doesn't quite follow our template yet:
- This issue doesn't appear to use one of our templates (Bug, Feature, or Task). Please open it using a template so the required details are captured.
Filling out the template helps reviewers understand and triage your contribution faster. Please edit the description to complete it. This message will disappear automatically once the template is followed.
You can find the template prompts by editing the description, or see [CONTRIBUTING.md](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) for the full contribution flow.
--
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: notifications-unsubscribe@texera.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org