Discussion

Ask HN: Keeping track of random stack traces

Every so often in a piece of software we're testing, you get a random crash. If you're unlucky it's a nice race condition, hasn't happened 50 times in a row, then boom, it happens again.

In terms of tracking it for the future, what suggestions do people have? I can backlog it as a bug, but it's not going to be easily searchable. A dev could pick it up, but without a method to reproduce, it's not easily fixed in a sprint either.

And it's also hard to know if it gets fixed in the future either!

But it's also a crash, and I personally hate not documenting them, no matter how rare. But I'd like a better way to manage it.

19 points beatthatflight 6 years ago 9 comments

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton