Open Atemu opened 1 month ago
thx for the report. I witness something like that regularly myself. Not sure yet what exactly is going on there.
As a workaround, you could at least consider a build/substitute to be done when a dependent starts realising.
I hope we can find a better solution.
This happened during a remote store + remote build (
--store ssh-ng://machine
where the store machine has remote builders configured).nom says it's substituting some paths whose dependents have already finished building which obviously can't be correct.
Speculation:
This might be due to the fact that the path was already present on the remote (but not the local machine nom runs on) and therefore isn't considered?