In my Python/Postgres work, unit tests don't catch lock behavior, so I run migrations against a disposable Postgres container in CI. Keeping the failing board trace with the exact firmware revision sounds like the same kind of evidence when a simulator and the board disagree. The board being the reference makes sense to me.