pycache: Allows tests to fail the first time and pass all subsequent ones
I had a test in which i was accessing memory that i was not supposed to.
The CI was failing every single time i would run it.
I tried to reproduced the same container locally, and my test failed the first time, because the memory that accessed wrongly was giving me garbage. All subsequent times i executed the test, it was passing because the invalid memory location instead of having garbage now it included always 0.
This was cause because the first time there was no pycache, and all subsequent ones, there was pycache.
To reproduce build:
- Build fedora34_mpi_ospray_python_qt_tbb:
- In vtkOrientPolyData::TraverseAndOrder comment out the folowing code:
if (npts < 3) { continue; }
- Execute VTK::FiltersGeneralPython-tableBasedClip
This can potentially affect all python flaky CI tests, that fail once in while, because a previous test might create the pycache and then they access it, so instead of garbage you know get valid results.
One idea would be to disable the creation of pycache for CI.
@ben.boeckel @ryan.krattiger1 @mwestphal @cory.quammen @berkgeveci @jaswant.panchumarti