boomanaiden154 wrote: @mysterymath In case you're unaware, the CI Checks workflow is failing/stuck queuing because these PRs haven't been rebased in the past couple weeks. We made some changes that require updates from the workflow definitions in `main`.
Normally these things get autopropagated to PRs if they're based on `main`, but they don't here since you're working on a stack. We should probably add some information on these failure modes to the CI documentation that we have yet to write... Commenting here mainly because this shows up weird on our monitoring (https://llvm.grafana.net/public-dashboards/21c6e0a7cdd14651a90e118df46be4cc). No action needed on your end though if you don't currently care about the CI results. https://github.com/llvm/llvm-project/pull/147426 _______________________________________________ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
