in the new CI pipeline based on GitLab runner, we have hit the situation where two scripts run at same time creating races in accessing ~/.crab3 cache file.
Should modify test script so that every crab command explicitly uses -d <directory> option.
And also point CRAB3_CRAB_CACHE to /dev/null to avoid possible access conflicts, see https://github.com/dmwm/CRABClient/issues/5337
[ ] remove the now duplicated code from checkStatus{}
That will allow running CCV in parallel with other tests.
CV is not straightforward, since having -d option or not should ideally part of the test itself.
It looks to me that ST test is safe on this regard. But should be reviewed.
in the new CI pipeline based on GitLab runner, we have hit the situation where two scripts run at same time creating races in accessing ~/.crab3 cache file.
Should modify test script so that every crab command explicitly uses
-d <directory>option. And also point CRAB3_CRAB_CACHE to /dev/null to avoid possible access conflicts, see https://github.com/dmwm/CRABClient/issues/5337remakeTask{}to https://github.com/dmwm/CRABServer/blob/v3.241018/test/testUtils.py (basically the first lines of currentcheckStatus{}: do a crab remake and returns directory name-d ...to each command.checkStatus{}That will allow running CCV in parallel with other tests. CV is not straightforward, since having
-doption or not should ideally part of the test itself.It looks to me that ST test is safe on this regard. But should be reviewed.