Skip to main content

Module lifecycle

Module lifecycle 

Source
Expand description

Crash-safe run publication, recovery and explicit retention.

Deletion targets are derived from a trusted project root. Large trees are atomically moved into durable trash; recursive unlinking is a separate, retryable operation that the CLI can run in a detached child.

Structs§

Archived
What a frontend that still holds the run it archived hands publication, so it need not read the archive back: the analysis of the archived request, and the assertion inputs archived beside it. Each must be what the archive gives; a frontend that cannot say so leaves it out.
CleanupOptions
CleanupResult
ProjectLock
RunState

Enums§

LifecycleError
RunStateStatus

Functions§

clean_storage
cleanup_storage_locked
finalize_published_run
interrupt_run_state
keep_failed_evidence
Keep what a run measured when Supercov itself is what failed.
note_kept_evidence
Say where a failed run’s evidence was kept, on the failure itself.
publish_archived_run
publish_run for a frontend that holds what it archived; see Archived.
publish_run
Publish immutable run evidence with its source manifest cache and per-test execution record together.
recover_abandoned_runs
remove_stored_tree_deferred
sweep_trash
Retryable trash unlinking. Public commands execute this in a child.
update_run_state
write_run_state