jgoeders
commented
2 months ago We don't want two conformal tasks to run in parallel during a ninja build, as the code currently copies things to the same temporary location in the CAEDM machine. How are we handling this right now?
A proper solution would be to remove the lock, but have temp directory locations on the remote machine so that nothing is ever clobbered.
The conformal lock found in bfasst/locks.py seems to only be locking the use of conformal on the client side. If this is an artifact from back when all outputs were being dumped in the same directory across multiple designs, then it should be removed.