vinny/CMOnet
Watch
1
0
Fork
You've already forked CMOnet
 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Lab runs note when a reload's new timeline started #148

Manually merged
vinny merged 0 commits from vinny/reload-timeline into master 2026-10-17 10:40:55 -04:00 AGit
Conversation 0 Commits - Files changed -
vinny commented 2026-10-17 10:39:40 -04:00
Owner
Copy link

Summary

  • A save_reload or load_alternate fault in a lab run now keeps timeline_seconds: how long after the reload CMOnet started a new timeline, when one follows within five minutes. The runner also logs timeline after reload.
  • Why: lab run 10 (trial 7, tpl-resilience-reload-alternate) recorded the save reload as recovered in 1.4 s. The save is reloaded under the name CMO already had, so CMOnet's first read after the load counts as recovery. The world cache's new scenario_id then started CMOnet's new timeline 26 s later (decision 8), and the order had to be given again. The run record did not show that.
  • Recovery timing and the fault_recovery_seconds metric are unchanged.

Test plan

  • tests/test_laboratory_runs.py::test_a_reload_notes_when_cmonet_started_its_new_timeline
  • tests/test_laboratory_runs.py
  • Full tools/check.py --rev in the background

🤖 Generated with Claude Code

## Summary - A `save_reload` or `load_alternate` fault in a lab run now keeps `timeline_seconds`: how long after the reload CMOnet started a new timeline, when one follows within five minutes. The runner also logs `timeline after reload`. - Why: lab run 10 (trial 7, tpl-resilience-reload-alternate) recorded the save reload as recovered in 1.4 s. The save is reloaded under the name CMO already had, so CMOnet's first read after the load counts as recovery. The world cache's new `scenario_id` then started CMOnet's new timeline 26 s later (decision 8), and the order had to be given again. The run record did not show that. - Recovery timing and the `fault_recovery_seconds` metric are unchanged. ## Test plan - [x] `tests/test_laboratory_runs.py::test_a_reload_notes_when_cmonet_started_its_new_timeline` - [x] `tests/test_laboratory_runs.py` - [ ] Full `tools/check.py --rev` in the background 🤖 Generated with [Claude Code](https://claude.com/claude-code) 
A save reloaded under its own name reads at once, so lab run 10's save
reload "recovered" in 1.4 s, while the world cache's new scenario_id
started CMOnet's new timeline 26 s later (decision 8), which the run
record did not show. A reload's fault now keeps timeline_seconds when a new
timeline follows within five minutes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Version 0.7.91 (reload-timeline)
Some checks failed
check / check (ubuntu-latest) (push) Has been cancelled
Details
check / check (windows-latest) (push) Has been cancelled
Details
check / check (windows-latest) (pull_request) Has been cancelled
Details
check / check (ubuntu-latest) (pull_request) Has been cancelled
Details
381cfd54d6
vinny manually merged commit 381cfd54d6 into master 2026-10-17 10:40:55 -04:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
vinny/CMOnet!148
No description provided.