Conversation
|
The merge queue now working on the right things I think: https://github.com/rust-ndarray/ndarray/actions/runs/8215462578 I listed the required checks in branch protection. I could list tests, cross_tests as those entries (not each test matrix entry, that resolves that problem for me). And mark those as being skipped for regular PR check (see the yaml file). Too early for bors-ng to be deprecated seeing how this works(!) 🙂 |
IIRC, in PyO3 we solved this by having a single job collect the state of all the other jobs (which I think is also the usual approach applied with bors). |
|
Oh, it ran all the right things but the required checks don't work like this. It autocompleted to tests and cross_tests for the required tests in the UI, but in CI it expands to the matrix of tests so the names are tests (stable) and so on. Everything's finished but it is still waiting. |
github-merge-queue
bot
removed this pull request from the merge queue due to no response for status checks
bluss
force-pushed
the
ci
branch
5 times, most recently
from
ed6e9bf to
b4440c3
Compare
Originally contributed by @messense in pyo3, copied their solution with thanks.
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
2 participants
Adopt conclusion job that summarizes ci status.
Originally contributed by @messense in pyo3, copied their solution with thanks.