FLIGHTOPS

← back to the bench

RECORDINGS

Every failure leaves a recording. Make it a test.

Triage finds the failure window and says where to look: one publisher, the whole graph, or the clock. The window becomes a replay fixture that guards the fix on every future change.

EVIDENCE

/cmd_vel dropout

2 Aug 2026 · silent for 6.05 s

triage: single publisher

31.6 s of recording

12 sof stimulus: the failure window only

34,630 messages

120messages on one topic

3.9 MB session

4.5 KBin git, beside the code it guards

FAILbug back in: odom_holds_rate

PASSfix in: Humble and Jazzy

The guards you already have were written for the failures you already had.The /cmd_vel publisher stopped for 6.05 s. The existing guards stayed green. The new fixture did not.

Triagesplashdown triage · three failure classes

Stats, slice, assert, queryoffline · ≤ 300 s · ≤ 10,000 messages

Fixtures and replaysplashdown fixture · splashdown replay

Managed recordingflightops record · retention · pins

Playback lanesevery topic and gap, one timeline · key 8

Reproduction packageshashed, offline bundles · flightops handoff

NEXT DRAWER