Skip to content

Bugfix: loops checkpointed before 2026.10.22 could not resume - #44

Merged
seamm merged 1 commit into
mainfrom
dev
Oct 22, 2026
Merged

seamm merged 1 commit into
mainfrom
dev

Conversation

@paulsaxe

Copy link
Copy Markdown
Contributor
  • A job with a loop that was checkpointed before 2026.10.22 refused to resume
    unless its cores per iteration was changed to automatic. It now resumes
    unchanged too (needs seamm 2026.10.22.1). Its other settings of how the
    iterations run must still be as they were.
  • The user guide now says that a resume refused because a setting changed runs
    nothing, rather than starting the job from the top.

CI fails until seamm 2026.10.22.1 is released (molssi-seamm/seamm PR above); rerun it then.

🤖 Generated with Claude Code

cores per iteration lists 1, its default until 2026.10.22, as a former
default (needs seamm 2026.10.22.1). The user guide now says a refused
resume runs nothing.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@paulsaxe paulsaxe added the bug Something isn't working label Oct 22, 2026
@paulsaxe
paulsaxe requested a review from seamm October 22, 2026 16:15

@seamm seamm 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.

LGTM

@seamm
seamm merged commit fe38953 into main Oct 22, 2026
8 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants