New issue 14 by ddor...@google.com: Multi-threaded Windows coverage builds
may fail with Permission denied on PDB file
http://code.google.com/p/swtoolkit/issues/detail?id=14
What steps will reproduce the problem?
1. hammer -j2 MODE=coverage-win
What is the expected output? What do you see instead?
Expect: Build completes successfully
Instead: Build may fail with "Permission denied" error on random PDB files.
This never fails when using hammer without -j#.
What version of the product are you using? On what operating system?
0.9.1
Windows XP SP3
Please provide any additional information below.
Below are two separate instances of this happening.
(1)
Install file: "scons-out\coverage-win\obj\tools\ApplyTag\ApplyTag.exe" as
"scons-out\coverage-win\staging\ApplyTag.exe"
copy "scons-out\coverage-win\obj\tools\ApplyTag\ApplyTag.pdb" "scons-
out\coverage-win\staging\ApplyTag.pdb"
1 file(s) copied.
copy "scons-out\coverage-win\obj\tools\ApplyTag\ApplyTag.exe" "scons-
out\coverage-win\staging\ApplyTag.exe"
1 file(s) copied.
C:\tools/vc_80/files/team_tools/performance_tools/vsinstr.exe /COVERAGE
"scons-out\coverage-win\staging\ApplyTag.exe"
<snip>
scons: *** [scons-out\coverage-win\staging\ApplyTag.pdb] C:\omaha\scons-
out\coverage-win\staging\ApplyTag.pdb: Permission denied
Microsoft (R) VSInstr Post-Link Instrumentation 8.0.50727 x86
Copyright (C) Microsoft Corp. All rights reserved.
File to Process:
C:\omaha\scons-out\coverage-win\staging\ApplyTag.exe --> C:\omaha\scons-
out\coverage-win\staging\ApplyTag.exe
Original file backed up to C:\omaha\scons-out\coverage-
win\staging\ApplyTag.exe.orig
Successfully instrumented file C:\omaha\scons-out\coverage-
win\staging\ApplyTag.exe.
"C:\tools\platformsdk_vista_6_0\files\bin\signtool.exe" sign /f
"C:\omaha\data/OmahaTestCert.pfx" /p "test" /t
"http://timestamp.verisign.com/scripts/timestamp.dll" "scons-out\coverage-
win\staging\ApplyTag.exe"
Done Adding Additional Store
Successfully signed and timestamped: scons-out\coverage-
win\staging\ApplyTag.exe
scons: building terminated because of errors.
(2)
Successfully signed and timestamped: scons-out\coverage-
win\staging\GoogleUpdate_signed.exe
Waiting for access to C:\omaha\scons-out\coverage-
win\obj\testing\omaha_unittest.exe...
Install file: "scons-out\coverage-
win\obj\google_update\GoogleUpdate_unsigned.exe" as "scons-out\coverage-
win\staging\GoogleUpdate_unsigned.exe"
copy "scons-out\coverage-win\obj\google_update\GoogleUpdate_unsigned.pdb"
"scons-out\coverage-win\staging\GoogleUpdate_unsigned.pdb"
1 file(s) copied.
copy "scons-out\coverage-win\obj\google_update\GoogleUpdate_unsigned.exe"
"scons-out\coverage-win\staging\GoogleUpdate_unsigned.exe"
1 file(s) copied.
C:\tools/vc_80/files/team_tools/performance_tools/vsinstr.exe /COVERAGE
"scons-out\coverage-win\staging\GoogleUpdate_unsigned.exe"
Microsoft (R) VSInstr Post-Link Instrumentation 8.0.50727 x86
Copyright (C) Microsoft Corp. All rights reserved.
File to Process:
C:\omaha\scons-out\coverage-win\staging\GoogleUpdate_unsigned.exe -->
C:\omaha\scons-out\coverage-win\staging\GoogleUpdate_unsigned.exe
Original file backed up to C:\omaha\scons-out\coverage-
win\staging\GoogleUpdate_unsigned.exe.orig
scons: *** [scons-out\coverage-win\staging\GoogleUpdate_unsigned.pdb]
C:\omaha\scons-out\coverage-win\staging\GoogleUpdate_unsigned.pdb:
Permission denied
Successfully instrumented file C:\omaha\scons-out\coverage-
win\staging\GoogleUpdate_unsigned.exe.
scons: building terminated because of errors.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings