-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiling 10.15.3 failing intermittently in custom build steps #27025
Comments
bnoordhuis
added a commit
to bnoordhuis/io.js
that referenced
this issue
Mar 31, 2019
It was reported that parallel builds on Windows sometimes error because of missing intermediate files. On closer inspection I noticed that some files are copied from src/ to the intermediate build directory in a way where they don't participate in dependency resolution. Put another way, the build system doesn't know to wait for the copy to complete because we don't tell it to. Fix that by not copying around files but instead making the script that processes them a little smarter about where to find them and where to store the results. Fixes: nodejs#27025
bnoordhuis
added
windows
Issues and PRs related to the Windows platform.
build
Issues and PRs related to build files or the CI.
labels
Mar 31, 2019
@danielgindi Can you check if #27026 fixes the issue for you? Thanks. |
@bnoordhuis that did it! thanks :-) |
@bnoordhuis You might want to |
@bnoordhuis Sorry, but it still fails occassionaly:
|
BethGriggs
pushed a commit
that referenced
this issue
Apr 9, 2019
It was reported that parallel builds on Windows sometimes error because of missing intermediate files. On closer inspection I noticed that some files are copied from src/ to the intermediate build directory in a way where they don't participate in dependency resolution. Put another way, the build system doesn't know to wait for the copy to complete because we don't tell it to. Fix that by not copying around files but instead making the script that processes them a little smarter about where to find them and where to store the results. PR-URL: #27026 Fixes: #27025 Reviewed-By: Eugene Ostroukhov <[email protected]> Reviewed-By: Richard Lau <[email protected]> Signed-off-by: Beth Griggs <[email protected]>
BethGriggs
pushed a commit
that referenced
this issue
Apr 10, 2019
It was reported that parallel builds on Windows sometimes error because of missing intermediate files. On closer inspection I noticed that some files are copied from src/ to the intermediate build directory in a way where they don't participate in dependency resolution. Put another way, the build system doesn't know to wait for the copy to complete because we don't tell it to. Fix that by not copying around files but instead making the script that processes them a little smarter about where to find them and where to store the results. PR-URL: #27026 Fixes: #27025 Reviewed-By: Eugene Ostroukhov <[email protected]> Reviewed-By: Richard Lau <[email protected]> Signed-off-by: Beth Griggs <[email protected]>
BethGriggs
pushed a commit
that referenced
this issue
Apr 10, 2019
It was reported that parallel builds on Windows sometimes error because of missing intermediate files. On closer inspection I noticed that some files are copied from src/ to the intermediate build directory in a way where they don't participate in dependency resolution. Put another way, the build system doesn't know to wait for the copy to complete because we don't tell it to. Fix that by not copying around files but instead making the script that processes them a little smarter about where to find them and where to store the results. PR-URL: #27026 Fixes: #27025 Reviewed-By: Eugene Ostroukhov <[email protected]> Reviewed-By: Richard Lau <[email protected]> Signed-off-by: Beth Griggs <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running
vcbuild.bat
on a clean clone - fails, due toobj/global_intermediate/node_protocol.pdl
not existing, or other such file inglobal_intermediate
.A second run on
vcbuild.bat
succeeds!I've narrowed it down to the default
/m:2
.The custom build steps in the
vcxproj
are not configured in a way that they depend on each other. The only dependency defined is their order in the project file, and they are configured as single items in the project with a custom build step on each of them.The result is that with multiple CLs running, the ordering is messed up. Because the factor is 2 concurrent CLs, a second run always succeeds.
I've also tried a workaround with
NUMBER_OF_PROCESSORS=1
in the env, but the shell does not allow such an override.The text was updated successfully, but these errors were encountered: