Executables in Bazel can contain root symlinks in their runfiles trees.
Those can have arbitrary paths that point at arbitrary files. Importantly, different executables can contain the same key with different values in their own root_symlinks.
When rules_multirun is used on binaries that contain conflicting root_symlinks, entries with the same key overwrite each other when the runfiles are merged.
I'm not sure if this issue has a real solution, outside of making the paths in root_symlinks unique for each binary, but I'd like to know if any other workarounds or ideas exist.
Executables in Bazel can contain root symlinks in their runfiles trees.
Those can have arbitrary paths that point at arbitrary files. Importantly, different executables can contain the same key with different values in their own root_symlinks.
When rules_multirun is used on binaries that contain conflicting root_symlinks, entries with the same key overwrite each other when the runfiles are merged.
I'm not sure if this issue has a real solution, outside of making the paths in
root_symlinksunique for each binary, but I'd like to know if any other workarounds or ideas exist.