What is flight recorder?
A flight recorder is a per-episode log of every command executed and every file diff produced, kept so a failed episode can be read rather than guessed at.
Debugging a batch failure without one means re-running the episode and hoping it fails the same way. With one, the flagged episodes in a validity report are openable: exact commands, exit codes, output, and what changed on disk.
Promigence keeps each failed episode for 7 days by default, so you can open it or re-run it with promigence run replay.
Related
This is one of the terms in the Promigence glossary.
Run your own workload on it, free
Send a repo and the command you run against it, whatever that is: an eval suite, an RL rollout, a CI job, a queue of coding tasks. We build the environment once, run it a thousand times, and send back the timings, the failures and an exact price. Free, once, on your real workload.
- 1,000 runs of your own command, on your own repo
- What each one cost in wall clock, and anything that failed
- Whether a failure was your code or the environment
- An exact price for your real volume
Not ready to hand over a repo? Read the quickstart or check the numbers first.