Post

noisy test failures burn hours: people reread the same logs, retry jobs to see if a failure disappears, and slowly stop trusting failures that point at something worth fixing. one approach: give each failure a stable identity you can compare over time. depot.dev/blog/failure...

depot.devFailure fingerprints: Comparing test failures over timeTo make recurring test failures easier to reason about we needed to include historical context. Here's how we derive a stable identity for each test and a fingerprint for each failure, so you can tell...

0 reposts0 likes

No replies yet.