(In reply to Jonathan Druart from comment #26) > There is something terribly wrong with this test file, the cronjob script is > run outside the transaction and so changes are effective.
Created attachment 125800 [details] [review] Bug 24326: The garbage man is your friend
Talking about bug titles, dcook ?
I do agree those tests should not have been pushed. 3 years later we are still missing the "clean ups could be handled separately" part. However the tests are there and can be useful, Jenkins could back us is something is going wrong. But for devs it's really bad. We could use the RUN_TESTS_AND_EXIT flag set by Jenkins: The tests would warn and exit early (exit 0) if the env var is not set. Something better to suggest?
What is the issue with the tests?
See comment 0: > the cronjob script is run outside the transaction and so changes are effective.
I didn't find any occurrence of RUN_TESTS_AND_EXIT in the codebase, so not sure if we have done similar before, but if we can make sure these are only run on by the automated tests, it would be helpful.