schedulertest: CHASM scheduler lifecycle driver harness#10726
Draft
davidporter-id-au wants to merge 3 commits into
Draft
schedulertest: CHASM scheduler lifecycle driver harness#10726davidporter-id-au wants to merge 3 commits into
davidporter-id-au wants to merge 3 commits into
Conversation
CreateSchedulerFromMigration stored whatever LastCompletionResult the migrated
V1 state carried, which is nil when the schedule had no prior completion (e.g.
migrated before its first action) — convertLastCompletionLegacyToCHASM returns
nil in that case. InvokerExecuteTaskHandler.startWorkflow then dereferences
lastCompletionState.Success/.Failure unconditionally, panicking on the first
workflow start after migration.
The normal CreateScheduler/NewScheduler path defaults to a non-nil empty
&schedulerpb.LastCompletionResult{}, so it never hit this. Default to the same
non-nil empty value in CreateSchedulerFromMigration.
Found by the V2->V1->V2 migration round-trip test.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
(cherry picked from commit 23ad378b19a638df2603c47c0e3a806e9877bf2e)
Test drivers that step a component forward need to invoke node-level task dispatch (EachPureTask/ExecuteSideEffectTask) and inspect accumulated physical tasks, which the Engine API did not expose. Add: - NodeForRef / BackendForRef accessors on the in-memory Engine. - WithNodeBackendDecorator option, applied to each execution's MockNodeBackend at creation time, so callers can supply handlers the default leaves unset (e.g. HandleGetNamespaceEntry, or a constant transition counter). All additive and default-nil; existing chasmtest users are unaffected. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> (cherry picked from commit aeddc4227acc0ec1c8a8b6b0034efa0d4c6bc42b)
Add a harness that builds a real CHASM scheduler on a chasmtest.Engine and steps it forward through every task it schedules for itself, advancing a controllable clock. Pure tasks dispatch via Node.EachPureTask and side-effect tasks via Node.ExecuteSideEffectTask (the production dispatch paths). The driver exposes Step/RunToQuiescence, Pause/Unpause/TriggerImmediately/MigrateToWorkflow operations, a Snapshot of observable state, and an AfterStep hook. This lives in a non-test package so property and migration tests can import it. library.go mirrors the in-package fixtures (NewTestLibrary, DefaultSchedule, ...) but exported and wired with the mock clients the side-effect handlers need. Smoke tests cover the three settled behaviors: a running interval schedule ticks forever, a paused schedule is held open and keeps ticking, and a schedule with no remaining actions idles then closes. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> (cherry picked from commit 77342fdbbdf5ef7fadaa16553a87c496edb2db81)
This was referenced Jun 16, 2026
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
1 participant
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.
What
Adds a test harness that builds a real CHASM scheduler on a
chasmtest.Engineand steps it forward through every task it schedules for itself, advancing a controllable clock. Pure tasks dispatch viaNode.EachPureTaskand side-effect tasks viaNode.ExecuteSideEffectTask(the production dispatch paths). The driver exposesStep/RunToQuiescence,Pause/Unpause/TriggerImmediately/MigrateToWorkflow, aSnapshotof observable state, and anAfterStephook.It lives in a non-test package (
chasm/lib/scheduler/schedulertest) so the property and migration tests later in the stack can import it.Also adds two small additive helpers to
chasm/chasmtest(used by the driver):NodeForRef/BackendForRefaccessors and aWithNodeBackendDecoratoroption. Both default-nil; existing chasmtest users are unaffected.Smoke tests cover the three settled behaviors: a running interval schedule ticks forever, a paused schedule is held open and keeps ticking, and a schedule with no remaining actions idles then closes.
Stack
Stacked on #10725 (the bugfix). The diff shown against
mainis cumulative — the net-new change here is the chasmtest +schedulertestdriver/library/smoke-test commits.Test plan
go test ./chasm/lib/scheduler/schedulertest/ -run TestDriver🤖 Generated with Claude Code