Skip to content

test(queue): wait on signals, not clocks -- queue_depth, codex_steering, compaction_stop, taskq_admission - #19496

Merged
iamwhatever merged 1 commit into
mainfrom
unflaky/wait-migrate-queue
Oct 14, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
unflaky/wait-migrate-queue

Conversation

@CrysisDeu

@CrysisDeu CrysisDeu commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: Four queue/steering backend test files wait on the signals their code emits, never on a guessed number of seconds.

These four files held 140 short fixed waits -- asyncio.wait_for(..., 5/10/20), .result(timeout=...), asyncio.timeout(5), and 5 ms poll loops. Each one bets that a CI runner finishes a store cancel, a dispatch, a compaction, or a steer inside a number tuned on a fast machine; a slow shard loses the bet and reds a pull request that never touched this code.

Why it matters

A lost clock bet in one of these files reds an unrelated PR, and the failure names a timeout, not a cause. Zero ratchet-counted fixed waits here means each file is far less likely to fail for a reason it cannot name.

Not a goal

  • Changing what any test asserts, with ONE deliberate exception called out in "What changed": test_a_steer_proven_mid_turn_is_not_reported_consumed_if_the_turn_is_cut had its wait condition changed and an assertion added, because the straight migration silently broke that test's coverage (see below). This is a coverage fix, not a behavior change to the code under test.
  • Changing the product code under test.
  • Touching any other test file, or any other line of test/wait_discipline_baseline.txt.
  • Changing kiro_crew.testing.wait (the test: ratchet fixed short waits; add await_until and LoopHop helpers #19248 helpers are used as they are).

What changed (motivation → approach → change)

Every counted site now awaits the event, future or state the code under test emits, under the lost-run bound the helpers default to (half the test's own timeout), instead of a short number.

Per-file ratchet-counted site count in test/wait_discipline_baseline.txt, all four lines removed:

File Before After
test_queue_depth_reconcile.py 43 0
test_codex_steering_request.py 42 0
test_compaction_stop_declined.py 35 0
test_taskq_admission_integration.py 20 0

Each kind of wait, and the signal it now rides on:

Was Now rides on
wait_for(event.wait(), 2/5/10) on an asyncio.Event await_until(event, what=...) -- returns once the event the code sets is set
wait_for(task/future/gather, 5/10/20) the test holds await_until(signal, what=...) -- the test owns the task; the bound never cancels it
wait_for(<coroutine the test calls>, N) -- mgr.cancel(...), _dispatch_async_impl(...), reads.get(), real_post(...) _finished(coro, what) -- the coroutine becomes a task awaited with await_until under the bound, cancelled on every early exit as wait_for did
hand-rolled poll for _ in range(200): if cond: break; sleep(0.01) and async with asyncio.timeout(5): while not cond: sleep(0) async_wait_until(lambda: cond, describe=...) on the state the poll watched
while not session.semaphore._waiters: sleep(0) (wait for a parked claimant) until_parked(session.semaphore) -- reads the primitive's own parked-waiter count
asyncio.timeout(5) guarding a startedNewTurn/notice loop async_wait_until on the notice list

Deliberate coverage fix in test_codex_steering_request.py

One site is not a mechanical swap. test_a_steer_proven_mid_turn_is_not_reported_consumed_if_the_turn_is_cut cuts the turn (reject / cancel) while it is still live, then checks the proven steer is not reported consumed. The original guard was a 2 s bounded poll of "text_chunk" in kinds and handle._queue.empty() that, in practice, never became true (codex buffers the chunk to the terminal, so kinds only fills at the end) -- the loop just ran out after 2 s and the cut landed mid-turn by luck of timing. A straight migration to async_wait_until(that condition) only becomes true at the prompt's own 5 s timeout, by which point the turn is already complete and the reject/cancel path is never exercised: the test would pass without testing anything, and its runtime jumped 2 s → 5 s.

The fix waits on the real mid-turn signal -- handle._steers_proven non-empty AND handle._queue.empty() (steer proven, chunk taken off the queue, not yet yielded) -- and then asserts "complete" not in kinds and "text_chunk" not in kinds before cutting, so the test now fails by name if the cut ever lands after the turn ended. Verified: removing the self._turn_steering_denied guard from _release_proven_steers in acp/session_handle.py turns the [denied] case red on this head (it stayed green before the fix); runtime is back to 0.03 s. This is a change to what the test covers, made on purpose.

The baseline diff (the only change to test/wait_discipline_baseline.txt): the four lines above are removed, no other line moves.

Waits still present after this PR

"Zero" above means zero ratchet-counted sites (the ratchet counts wait_for / asyncio.timeout / .result(timeout) under 30 s and sleep(0<N<5) inside a loop). Two shapes the ratchet does not count still live in test_compaction_stop_declined.py and are left as tracked debt, not silently claimed gone:

  • asyncio.sleep(0.05) permit-holds and failure-path barriers (:202, :483, :548, :552, :1682) -- a parked claimant deliberately holds the turn permit for a span, or a failure path advances into _await_cotenants; neither is a signal barrier until_parked fits.
  • done, _ = await asyncio.wait({task}, timeout=5); assert done (:2591, :2621) -- already a bounded lost-run wait on the task finishing.

Also, the _finished() wrapper is copied into three of the four files rather than living in kiro_crew.testing.wait (changing that module is out of this PR's goal, and three in-flight sibling PRs build on it).

Both are tracked in #20209 and are out of this PR's frozen goal (the 140 counted sites). No # flake-ok marker was added.

Backwards compatibility

Compatible: test-only change; no product code or public symbol moves, and every file-local helper keeps its name and signature.

Removes nothing: the only removed lines are these four files' own entries in a test-only ratchet baseline, which the gate reads as a count of zero.

Tests

  • The four migrated files: all tests keep their assertions (plus the one added coverage assertion above); 409 passed locally after rebasing on current main, and the four files passed on repeated runs with no new flakiness.
  • test/test_wait_discipline_ratchet.py: green on this branch; this PR's four lines are gone and no file rose because of this PR.
  • Static gates on the four files: black, isort, flake8 all clean.

Manual verification

N/A -- unit coverage sufficient: the change is to how these tests wait, and the tests themselves are the evidence (the coverage fix above is verified by the guard-removal check).

Related Issues

Part of #19248
Follow-up debt: #20209

@CrysisDeu
CrysisDeu requested review from a team and KiroCrewCaptain as code owners October 12, 2026 18:32
@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 0e9699a55b68d1957cf317fef6e7fa8501d60312 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Advisory — does not block merge.

@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ⏭️ skipped

Revision 0e9699a55b68d1957cf317fef6e7fa8501d60312 ships no reviewable capability (docs, tests or generated files only), so there is nothing to inventory. Advisory — does not block merge.

@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 12, 2026
@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 0e9699a55b68d1957cf317fef6e7fa8501d60312 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Check that the reworked test_a_steer_proven_mid_turn_is_not_reported_consumed_if_the_turn_is_cut actually fails when the _turn_steering_denied guard is removed, as the description says.

[DESIGN-REVIEWED] 0e9699a

Description read

[DESCRIPTION-READ] f2a4bf3c0f1a5cf64374bce5ce4a5c1c081177c65196182ed81553fe645330eb

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 0e9699a55b68d1957cf317fef6e7fa8501d60312 — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 0e9699a

Verdict parsed from the review's SHA-scoped output markers for commit 0e9699a55b68d1957cf317fef6e7fa8501d60312.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 0e9699a55b68d1957cf317fef6e7fa8501d60312: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 0e9699a55b68d1957cf317fef6e7fa8501d60312 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 0e9699a

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 0e9699a55b68d1957cf317fef6e7fa8501d60312: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 12, 2026
@CrysisDeu
CrysisDeu force-pushed the unflaky/wait-migrate-queue branch from addc922 to c14a768 Compare October 12, 2026 19:38
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 12, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of this migration is a clean win: every wait_for(x, N) now goes through await_until / _finished under the lost-run bound, the soft polls became asserting waits, and the baseline only drops the four touched files. The ratchet passes (39) and the four files pass (364) on this head.

One blocking issue in test_a_steer_proven_mid_turn_is_not_reported_consumed_if_the_turn_is_cut (test_codex_steering_request.py ~688-692). The new wait for "text_chunk" in kinds and handle._queue.empty() only becomes true when the turn hits its own prompt(timeout=5.0): with timing added, the condition turns true at 4.98 s with kinds already ['text_chunk', 'complete']. So the reject / cancel the test is about lands after the turn has ended and is never exercised, and the final asserts pass only because a timeout stop is never reported as consumed. The test's runtime also moved from about 2 s to about 5 s. Concretely, removing self._turn_steering_denied from the guard in _release_proven_steers (acp/session_handle.py ~3523) turns the [denied] case red on main but leaves it green on this head (only test_after_a_denied_approval_nothing_in_the_turn_is_reported_consumed still catches it). Please wait on a signal that holds while the turn is still live (for example the steer proven and the chunk taken off the queue, not yet yielded to the consumer), and assert complete is not in kinds before cutting the turn.

Non-blocking:

  • test_compaction_stop_declined.py still uses asyncio.sleep(0.05) as a barrier in a few places (around :200, :303, :368, :372, :1502, e.g. "inside _await_cotenants now") and two asyncio.wait({task}, timeout=5) calls (:2411, :2441). The ratchet does not count those forms, so they are worth migrating (until_parked fits) or naming as out of scope.
  • _finished() is copied into three files; it could live in kiro_crew.testing.wait.

The cancelled checks on this head are superseded duplicate runs; every workflow has a later successful run on the same SHA.

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 12, 2026
@CrysisDeu
CrysisDeu force-pushed the unflaky/wait-migrate-queue branch from c14a768 to d5246d3 Compare October 12, 2026 21:06
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Thanks for the careful read, and for pinning the exact failure mode.

Blocking — test_a_steer_proven_mid_turn_is_not_reported_consumed_if_the_turn_is_cut: fixed in d5246d3.

You were right: "text_chunk" in kinds and handle._queue.empty() only coincide when
the prompt's own 5 s timeout completes the turn, so the cut landed post-terminal and the
reject/cancel path never ran. The chunk is buffered to the terminal, so kinds has no
mid-turn signal at all. The wait now rides the internal mid-turn state the dispatch loop
leaves right after steer() returns True: handle._steers_proven non-empty AND
handle._queue.empty() (chunk taken off the queue, not yet yielded), then it asserts
"complete" not in kinds and "text_chunk" not in kinds before cutting — so the test now
fails by name if the cut ever lands after the turn ends.

Verification: the [denied]/[cancelled] cases now run in 0.03 s (was ~5 s), and with your proposed regression — deleting self._turn_steering_denied from the _release_proven_steers guard — [denied] goes red on this head and green again once restored. So the guard is exercised here again, not only by test_after_a_denied_approval_nothing_in_the_turn_is_reported_consumed.

Non-blocking 1 — remaining asyncio.sleep(0.05) / asyncio.wait({task}, timeout=5) in test_compaction_stop_declined.py: accepted-and-deferred (out of this PR's goal).

The ratchet does not count those forms and they are not among this PR's 140 sites; the
frozen goal is the counted-site burn-down. Several of the sleep(0.05) calls are also
deliberate time-holds, not signal barriers — a claimant holding the turn permit for a
duration
while the compaction's finally runs (:200, :1502) — so they are not clock
bets on a signal and until_parked does not fit them. I would rather not widen a green,
single-purpose PR; happy to file a deferred-finding issue for the barrier-shaped ones
(:303, :368, :372) if you would like them tracked.

Non-blocking 2 — hoist _finished() into kiro_crew.testing.wait: rebutted (out of goal).

This PR's "Not a goal" explicitly excludes changing kiro_crew.testing.wait (the #19248
helpers are used as-is). Hoisting a shared wrapper into that module is a good idea but is a
separate change that touches a file three in-flight sibling PRs also build on; doing it here
would serialize them behind this PR. Better as its own follow-up once the batch lands.

@CrysisDeu
CrysisDeu requested a review from buluoray October 12, 2026 21:07
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: passed Eligible automated validation passed for the current revision readiness: checking Automated validation is still running labels Oct 12, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor

Reviewed, not approving yet: @buluoray's CHANGES_REQUESTED review is still open. Please re-review (or dismiss it) once you agree it is met; I would approve after that. My read: This test-only PR replaces 140 short fixed waits in four backend test files with waits on the events, futures and state the code emits (await_until, async_wait_until, until_parked), and drops those four files' lines from the wait-discipline baseline. No assertion or product code changes. buluoray's blocking point on c14a768 was that the steer-cut test only became true after the turn's own 5 s timeout, so the reject/cancel path never ran. On head d5246d3 the test waits on _steers_proven being set with the queue empty, then asserts that neither complete nor text_chunk is in kinds before it cuts the turn. I checked that the fix works: I checked out the head and removed self._turn_steering_denied from the _release_proven_steers guard (acp/session_handle.py:3523), and [denied] went red (['text_chunk', 'steer_consumed', 'complete']); with the line restored both cases pass in 0.03 s. The four files plus the ratchet pass on this head (403 passed, -n 4). The two non-blocking points have reasonable replies: the leftover sleep(0.05) holds are deferred, and hoisting _finished is excluded by the stated Not-a-goal. Each _finished copy cancels its task on early exit, as wait_for did. — crew-pr-reviewer (deep re-check)

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 13, 2026
@CrysisDeu
CrysisDeu force-pushed the unflaky/wait-migrate-queue branch from d5246d3 to 919869f Compare October 13, 2026 00:18
@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Oct 13, 2026
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: passed Eligible automated validation passed for the current revision readiness: checking Automated validation is still running labels Oct 13, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor

NO-REPOST: This test-only PR swaps 140 short fixed waits in four backend test files for waits on the events, futures and state the code under test emits (await_until, async_wait_until, until_parked), and drops those four files' lines from the wait-discipline baseline. The head moved from d5246d3 to 919869f, but that is a rebase onto main. I diffed all four files between the two SHAs. Three are byte-identical. The only change in test_compaction_stop_declined.py is tests main added in the meantime, and those are not in this PR's diff. The steer-cut fix I verified last time is unchanged: the test waits on _steers_proven with the queue empty, then asserts neither complete nor text_chunk is in kinds before cutting. Checks are green and base is main. The blocker is still procedural: buluoray's CHANGES_REQUESTED review from c14a768 is open and has not been re-reviewed or dismissed, though by my read its blocking point is fully met. @buluoray, please re-review or dismiss it, and I would approve after that. — crew-pr-reviewer (deep re-check)

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verdict: APPROVE at 919869f6db

What it fixes

This change moves four queue and steering test files off fixed sleeps and onto signal waits under the lost-run bound, and drops those four files from the wait-discipline baseline. Since my review on c14a768e1a, the PR has been rebased, and the only change to its own commit is the denied/cancelled steer test.

What I verified

  • The blocking point from my last review is fixed. In test/test_codex_steering_request.py:695-699, test_a_steer_proven_mid_turn_is_not_reported_consumed_if_the_turn_is_cut now waits on handle._steers_proven being non-empty and handle._queue.empty(). That condition holds while the turn is still live, because codex buffers the chunk until the terminal frame. Line 700 then asserts that neither complete nor text_chunk has reached the consumer before the reject or cancel lands. The cut now really happens mid-turn.
  • The call phase now takes 0.03 s. On the previous head it took about 5 s, because the test was waiting for the prompt's own timeout=5.0.
  • Mutation: I removed or self._turn_steering_denied from _release_proven_steers (src/kiro_crew/acp/session_handle.py:3523). This turns test_a_steer_proven_mid_turn_is_not_reported_consumed_if_the_turn_is_cut[denied] red (['text_chunk', 'steer_consumed', 'complete']), along with test_after_a_denied_approval_nothing_in_the_turn_is_reported_consumed. On c14a768e1a, only the second test went red.
  • The four touched files pass (370), and test_wait_discipline_ratchet.py passes (39).

Non-blocking follow-ups

  • The [cancelled] case of the same test does not pin the self._cancelled guard on its own. With that guard neutralised (line 3522), only test_a_cancelled_turn_reports_no_steer_consumed goes red. The cancelled case stays green because stopReason: "cancelled" is already caught by the reason != end_turn allowlist. The behaviour is still covered elsewhere; this note is only about which test pins which guard.

  • The items from my last review are still open:

    • test/test_compaction_stop_declined.py still uses asyncio.sleep(0.05) as a barrier at :202, :483, :548, :552 and :1682, and still has asyncio.wait({task}, timeout=5) at :2591 and :2621.
    • _finished() is still copied into three files.

    Either migrate these (until_parked fits the barrier cases) or name them as out of scope.

Not verified

  • I did not re-read CI on this head.
  • I did not re-run the full suite. I only ran the four touched files and the ratchet.

@iamwhatever iamwhatever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

REQUEST_CHANGES at 919869f. @buluoray's approval clears their earlier blocking finding, but the current-head Design concern remains unanswered. The steer-cut test deliberately changes its wait condition and adds an assertion. Please describe that coverage fix and correct the claim that no assertions changed. Also fix or track the two follow-ups in buluoray's review: remaining sleep/wait barriers in test_compaction_stop_declined.py, and the duplicated _finished helper. If deferred, open one issue per item and link both in the PR description. The description's 'Remaining short fixed waits ... none' must distinguish ratchet-counted waits from the waits still present. I verified the review, description, and source evidence; tests were not run locally. — crew-pr-reviewer (r99)

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: passed Eligible automated validation passed for the current revision labels Oct 14, 2026
…ng, compaction_stop, taskq_admission

Four backend test files bet on fixed short waits for things the code
signals. A slow CI shard loses the bet and reds an unrelated PR. Migrate
every counted site to a wait on the real signal, using the
kiro_crew.testing.wait helpers from #19248.

Site counts (test/wait_discipline_baseline.txt): all four lines removed.
  test_queue_depth_reconcile.py       43 -> 0
  test_codex_steering_request.py      42 -> 0
  test_compaction_stop_declined.py    35 -> 0
  test_taskq_admission_integration.py 20 -> 0

No test's intent changed; no assertion was weakened; no site moved to
another file. Part of the wait-discipline burn-down behind #19248.
@CrysisDeu
CrysisDeu force-pushed the unflaky/wait-migrate-queue branch from 919869f to 0e9699a Compare October 14, 2026 08:35
@CrysisDeu

Copy link
Copy Markdown
Contributor Author

Addressed all four items on head 0e9699a55b (rebased on current main 30bb0b3d).

(1) Design concern — the test's wait+assertion change is now named as a deliberate coverage fix. The body's "Not a goal" now carves out this one exception, and a new "Deliberate coverage fix in test_codex_steering_request.py" subsection explains it: the old 2 s poll of "text_chunk" in kinds and handle._queue.empty() never actually became true mid-turn (codex buffers the chunk to the terminal), so the reject/cancel cut landed mid-turn only by timing luck; a straight migration only becomes true at the prompt's 5 s timeout, after the turn is complete, so the path under test never ran. The fix waits on the real mid-turn signal (_steers_proven + queue.empty()) and asserts "complete"/"text_chunk" not in kinds before cutting. Verified by re-applying the guard-removal mutation: [denied] goes red on this head, green with the guard; runtime 5 s → 0.03 s.

(2) "Remaining ... none" corrected. The body now says zero ratchet-counted sites, and adds a "Waits still present after this PR" subsection listing the non-counted waits that remain.

(3) buluoray's two non-blocking follow-ups → tracked in #20209.

The test_compaction_stop_declined.py asyncio.sleep(0.05) sites (:202, :483, :548, :552, :1682) are deliberate permit-holds and failure-path barriers, not signal barriers until_parked fits; the asyncio.wait({task}, timeout=5) sites (:2591, :2621) are already bounded lost-run waits. The _finished() dedup belongs in kiro_crew.testing.wait, which this PR's goal excludes and three in-flight sibling PRs build on. Both are logged as debt in #20209 rather than churned into this PR.

(4) Re-requesting both reviewers.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 14, 2026

@iamwhatever iamwhatever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

APPROVE at 0e9699a.

All r99 items are now addressed. The description names the steer-cut change as a deliberate coverage fix, and the test waits on _steers_proven with the queue empty, then asserts the turn is still live before cutting (test_codex_steering_request.py#L710-L714). "Zero" now means zero ratchet-counted waits, and the uncounted ones are listed. Both deferred items, the remaining test_compaction_stop_declined.py holds/barriers and the copied _finished() helper, are tracked with their own sections in the assigned issue #20209, which the description links. Since 919869f the only change is a rebase adaptation to main's STEERING_ANSWER_WAIT_SECS rename. @buluoray's approval supersedes their earlier change request. The Design punchline is answered, and all checks on this head are green. No tests were run locally this round.

— crew-pr-reviewer (r100)

@iamwhatever
iamwhatever merged commit 32ff604 into main Oct 14, 2026
101 of 102 checks passed
@iamwhatever
iamwhatever deleted the unflaky/wait-migrate-queue branch October 14, 2026 16:21
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants