Skip to main content

Setting time and memory budgets

Simple Story

A pupil who never finishes must fail their own question rather than halt the whole examination.

This page is a stub

The outline below is the intended structure and is not yet written. Until it is, use the Policy Reference for the individual fields.

The situation​

The exercise needs a wall-clock and a memory ceiling, and it matters which of the two modes enforces them.

The policy fragment​

The smallest security-policy.yaml addition that solves it, shown in full so it can be pasted into an existing policy.

What this still forbids​

The operations the recipe deliberately does not enable, so the boundary stays visible.

The tempting wrong version​

Assuming the policy's resource limits bound a Postcompile run. They are generated but not yet dispatched there; @StrictTimeout is what applies.

Notes​

  • Check the recipe against both controls: the permitted operation must succeed, and the nearest forbidden neighbour must still be rejected.