rspec --bisect is a great tool for combatting test pollution (having one test pollute the test environment via database records, environment changes, etc) by having a systematic way of tracking down order-based failures. Instead of making this a reactive process that you run when your team is seeing these test pollution problems, we like to get ahead of the problem by actively running rspec --bisect on our test suite (via CirleCI) regularly, that way we have a quick path to finding a fix when it's introduced.
'rspec --bisect' takes a while! CircleCI has a configurable no_output_timeout that you can extend to support this, but unfortunately it has a hardcoded max, somewhere in the range of 5 hours IIRC
Extend the no_output_timeout to something larger, please!