Fix: drain SUB workers during scheduler test teardown - #1668
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe scheduler teardown fixture now drains SUB workers before shutdown. The teardown test submits a SUB group and verifies that both SUB workers run alongside NEXT_LEVEL workers. ChangesScheduler teardown coverage
Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
GroupSchedulerFixture.running and queued NEXT_LEVEL work.
Why
GroupSchedulerFixtureregisterssub_worker_aandsub_worker_b, but itsteardown previously drained only the NEXT_LEVEL workers.
Scheduler::stop()waits for
WorkerManager::any_busy(), which includes SUB workers, so anunfinished SUB dispatch could hang fixture teardown.
This is a follow-up to #1611 and addresses:
#1611 (comment)
Testing
TearDownDrainsCurrentAndQueuedDispatches: 100 iterations passed.test_scheduler: 62 tests passed.test_remote_endpointpassed when rerun outside because socket creation isrestricted inside the Codex sandbox.
clang-format --dry-run --Werrorpassed.