Gyp does not produce a warning or an error if there are two actions that both
write to the same file.
This caused a problem in the NaCl and Chrome builds which went undetected for a
long time and made the build flaky. NaCl's build was instantiating an action
twice (for 32-bit and 64-bit Windows targets), using the same output filename
twice. Occasionally these actions would be run concurrently, which would fail
because of Windows' file locking.
See http://code.google.com/p/nativeclient/issues/detail?id=1729 for the NaCl
bug.
Original issue reported on code.google.com by mseaborn@chromium.org on 27 Jul 2011 at 1:24
Original issue reported on code.google.com by
mseaborn@chromium.org
on 27 Jul 2011 at 1:24