I agree in general.
But if you dig into the issue I've encountered, the cause of the failure is
elusive, the tests that are implicated in triggering the failure are unrelated
the the actual cause, and those tests are still providing value where they're
succeeding. I don't want to disable them u
TL;DR - lets just define an env var to be practical about this, but
discourage its use.
All CI systems I've dealt with, whatever they're called, make it possible
to officially detect when running within one. Otherwise code that *needs*
to do so resorts to non-canonical extreme bespoke measures to
