It depends entirely on the reason for that 1/10 times. E.g. I had a test that hit a 3rd party sandbox that would go down occasionally. I could have mocked it t

It depends entirely on the reason for that 1/10 times. E.g. I had a test that hit a 3rd party sandbox that would go down occasionally. I could have mocked it to avoid this but I had way bigger fish to fry. The flakiness triggered a very specific error that we felt safe ignoring (other kinds of flakiness we would not ignore). The corresponding prod API never had issues. Sometimes it's a select statement without an order by in which case even if it's not strictly a bug but just quickly adding an order by solves the flakiness forever so you might as well. Sometimes it's a pretty terrifying race condition in the code that will absolutely crop up in prod.