Repository navigation
Release DeployBot v0.2.15 with concurrent integration CI - #39
Merged
Merged
Conversation
mberman84
marked this pull request as ready for review
June 22, 2026 00:58
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
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.
Summary
Regression evidence
The production-shaped Astro queue had two ready integration PRs. The first exact-head CI sat in GitHub Actions for 20 minutes, and DeployBot did not dispatch the second PR's CI because
settle_integration_checkswaited one PR at a time. The new regression test proves both dispatches happen before the first polling sleep.Verification
PYTHONPATH=src python3 -m unittest discover -s tests -q(206 tests)ruff check src testspython3 -m buildRelease notes
DeployBot v0.2.15 prevents one slow integration runner from starving later cumulative batches and makes the exact integration-CI wait visible in status.