This is because the tempest tests are cleaning up a fixture that was owned by the test (useFixture) by hand.
Then when useFixtures own addCleanup triggers calling fixture.cleanUp, the cleaned fixture is cleaned again - which now triggers an error. Previously there was a bug where:
f = Fixture()
try:
f.cleanUp() # ERROR - ok sure
except:
pass
f.setUp()
f.cleanUp()
f.cleanUp () # WTF no error
This is because the tempest tests are cleaning up a fixture that was owned by the test (useFixture) by hand.
Then when useFixtures own addCleanup triggers calling fixture.cleanUp, the cleaned fixture is cleaned again - which now triggers an error. Previously there was a bug where:
f = Fixture()
try:
f.cleanUp() # ERROR - ok sure
except:
pass
f.setUp()
f.cleanUp()
f.cleanUp () # WTF no error
would work.