No. But from the vibe of your note I'm guessing I don't even want to.😀

Yes but it was because I wasn't clearing in memory mock DB 🙃

Its that sinking hmmmm

This could be nothing (clear caches etc) or a terrible afternoon ahead (?????)

Yes. Sounds like muddied states for tests?

all too well

multi-threading, failure to cleanup mock data(base), assumptions based on prior test state. Seen it all :(

Yes. Or when it runs locally fine and you run it in the pipeline and it fails without any reason. Hated that and to this day i have not figured out why it failed.

Do you know the feeling of call the skip method on the test function?

I've had stubborm tests that just could not be fixed no matter what I did. CI can be hell sometimes

It is something like when you reach 95% at progress bar and,while you are realizing it is almost complete, it suddenly stuck at 97% forever .. so you have to stop everything and start to realize that something odd have to be overcome and understood ..

For us, it's often how slow the CI is. cpuset can be used to reproduce this...