ci: Dynamically re-gate heavy tests on PRs when no merge queue is active - #2363
Merged
Merged
Conversation
cgwalters
enabled auto-merge (rebase)
August 5, 2026 13:46
Collaborator
Author
|
OK let's get this one in and then cut another release to get the fix out for #2364 |
jeckersb
previously approved these changes
Aug 5, 2026
Our CI jobs were wired to the merge queue semantics, I broke this when dropping the merge queue requirement. xref bootc-dev#2177 Change the logic to detect a merge queue dynamically, then if we decide to flip back on the queue things should work the same as before. But here we need to run the tests. Also while we're here make use of the (new-ish) `ubuntu-slim` for jobs that are just computing state as that's cheaper and should be quicker to schedule. Assisted-by: AI Signed-off-by: Colin Walters <walters@verbum.org>
cgwalters
force-pushed
the
re-enable-required-jobs
branch
from
August 5, 2026 16:52
3d9bc6b to
3e5a9bd
Compare
Collaborator
Author
|
Ah and CI was failing here because I hadn't rebased, argh. Done now... |
Assisted-by: AI Signed-off-by: Colin Walters <walters@verbum.org>
Collaborator
Author
|
OK this needs one more stamp |
jeckersb
previously approved these changes
Aug 5, 2026
gursewak1997
previously approved these changes
Aug 5, 2026
This test has some issues currently, especially in the upgrade path. Since this does not affect the install/update flows, disable this test Signed-off-by: Pragyan Poudyal <pragyanpoudyal41999@gmail.com>
Johan-Liebert1
dismissed stale reviews from gursewak1997 and jeckersb
via
August 6, 2026 08:55
72428d1
Collaborator
|
I've disabled the UKI dumpfile test for now as it has other issues, especially in the upgrade path. upgrade/switch operations work, but the test itself needs some fixing. Also, I forgot to include the dumpfile print in the upgrade flow. I'll create another PR fixing that |
Johan-Liebert1
disabled auto-merge
August 6, 2026 08:57
Johan-Liebert1
approved these changes
Aug 6, 2026
Collaborator
Author
|
Argh, two more flakes. It's annoying one can't restart the tests until all have finished. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our CI jobs were wired to the merge queue semantics, I broke this when dropping the merge queue requirement.
xref #2177
Change the logic to detect a merge queue dynamically, then if we decide to flip back on the queue things should work the same as before. But here we need to run the tests.
Also while we're here make use of the (new-ish)
ubuntu-slimfor jobs that are just computing state as that's cheaper and should be quicker to schedule.Assisted-by: AI