| Issue |
151135
|
| Summary |
Merge via Graphite in rebase loop, probably related to pre-merge CI
|
| Labels |
infrastructure
|
| Assignees |
|
| Reporter |
ritter-x2a
|
Merging PRs via Graphite's web UI seems to run into pre-merge CI problems at the moment:
- PR #150392 ([Graphite link](https://app.graphite.dev/github/pr/llvm/llvm-project/150392)) has automatically rebased itself 9 times before merging (see the generated comment [here](https://github.com/llvm/llvm-project/pull/150392#issuecomment-3131445657))
- PR #150899 ([Graphite link](https://app.graphite.dev/github/pr/llvm/llvm-project/150899)) has so far rebased itself 7 times and is still in the merge process ([generated progress comment](https://github.com/llvm/llvm-project/pull/150899#issuecomment-3131445661)).
I started both merges at the same time via Graphite's web UI for merging (part of) a stack. Help would be much appreciated.
My best guess is that the CI checks were set to mandatory for merging (they are displayed that way in Graphite's UI, that seems new to me), and whenever a new commit lands in trunk while the CI is still running, the CI is cancelled (sending an email notification), Graphite automatically rebases, and restarts the CI, until there is a sufficiently long period where no new patch lands on trunk so that the CI can complete. If that's the case, that seems like a bad setup for LLVM, considering the frequency of contributions vs the turnaround time of the pre-merge CI.
![]()
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
