QuantumAttemptStatus¶
- class lsst.pipe.base.QuantumAttemptStatus(value, names=<not given>, *values, module=None, qualname=None, type=None, start=1, boundary=None)¶
Bases:
EnumEnum summarizing an attempt to run a quantum.
Attributes Summary
This quantum was not executed because an upstream quantum failed.
Execution of the quantum failed.
Task metadata was written for this attempt but logs were not.
This quantum was successfully executed.
The status of this attempt is unknown.
Attributes Documentation
- BLOCKED = 0¶
This quantum was not executed because an upstream quantum failed.
Upstream quanta with status
UNKNOWNorFAILEDare considered blockers;LOGS_MISSINGis not.
- FAILED = -1¶
Execution of the quantum failed.
This is always set if the task metadata dataset was not written but logs were, as is the case when a Python exception is caught and handled by the execution system. It may also be set in cases where logs were not written either, but other information was available (e.g. from higher-level orchestration tooling) to mark it as a failure.
- LOGS_MISSING = -2¶
Task metadata was written for this attempt but logs were not.
This is a rare condition that requires a hard failure (i.e. the kind that can prevent a
finallyblock from running or I/O from being durable) at a very precise time.
- SUCCESSFUL = 1¶
This quantum was successfully executed.
Quanta may be considered successful even if they do not write any outputs or shortcut early by raising
NoWorkFoundor one of its variants. They may even be considered successful if they raiseAnnotatedPartialOutputsErrorif the executor is configured to treat that exception as a non-failure. SeeQuantumSuccessCaveatsfor details on how these “successes with caveats” are reported.