You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/pipeline/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Key behaviors:
39
39
- After each step, the pipeline checks the latest `StepResult`. If it failed, the pipeline sets its status to `FAILED` and breaks.
40
40
- Unhandled exceptions set the status to `INTERRUPTED`.
41
41
- After all steps (or early exit), `finish_execution()` is called to assemble the final `GradingResult`.
42
-
- Sandbox cleanup always runs at the end, regardless of success or failure.
42
+
- Sandbox cleanup always runs at the end, regardless of success or failure, and destroys the sandbox used by that submission.
43
43
44
44
### PipelineExecution
45
45
@@ -191,7 +191,7 @@ When a step fails:
191
191
2. The pipeline detects the failure via `get_previous_step()` and calls `set_failure()`.
192
192
3. No further steps are executed.
193
193
4.`finish_execution()` is called — since the status is `FAILED`, `result` remains `None`.
194
-
5. Sandbox cleanup always runs: if a Sandbox step created a sandbox, it is released back to the pool regardless of pipeline outcome.
194
+
5. Sandbox cleanup always runs: if a Sandbox step created a sandbox, it is destroyed regardless of pipeline outcome, and the pool replenishes with a fresh container.
195
195
196
196
For unhandled exceptions, the status is set to `INTERRUPTED` and the same cleanup logic applies.
0 commit comments