New issue
Advanced search Search tips

Issue 610367 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2016
Cc:
h...@chromium.org
scottmg@chromium.org
r...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocking:
issue 82385



Sign in to add a comment

"LINK : fatal error LNK1207: incompatible PDB format in $foo.pdb; delete and rebuild" on win_clang bot while linking every now and then

Project Member Reported by thakis@chromium.org, May 9 2016 
https://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/18566/steps/compile%20%28without%20patch%29/logs/stdio
E:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /IMPLIB:./onc.dll.lib /DLL /OUT:./onc.dll /PDB:./onc.dll.pdb @./onc.dll.rsp
LINK : fatal error LNK1207: incompatible PDB format in 'E:\b\build\slave\win_clang\build\src\out\Debug_x64\onc.dll.pdb'; delete and rebuild

https://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/18558/steps/compile%20%28without%20patch%29/logs/stdio
FAILED: onc.dll onc.dll.lib 
E:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /IMPLIB:./onc.dll.lib /DLL /OUT:./onc.dll /PDB:./onc.dll.pdb @./onc.dll.rsp
LINK : fatal error LNK1207: incompatible PDB format in 'E:\b\build\slave\win_clang\build\src\out\Debug_x64\onc.dll.pdb'; delete and rebuild

https://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/18639/steps/compile%20%28without%20patch%29/logs/stdio
FAILED: upgrade_test.exe 
E:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /OUT:upgrade_test.exe /PDB:upgrade_test.exe.pdb @upgrade_test.exe.rsp
LINK : fatal error LNK1207: incompatible PDB format in 'E:\b\build\slave\win_clang\build\src\out\Debug_x64\upgrade_test.exe.pdb'; delete and rebuild

https://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/18657/steps/compile%20%28without%20patch%29/logs/stdio
FAILED: upgrade_test.exe 
E:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /OUT:upgrade_test.exe /PDB:upgrade_test.exe.pdb @upgrade_test.exe.rsp
LINK : fatal error LNK1207: incompatible PDB format in 'E:\b\build\slave\win_clang\build\src\out\Debug_x64\upgrade_test.exe.pdb'; delete and rebuild


https://build.chromium.org/p/tryserver.chromium.win/builders/win_clang/builds/18539/steps/compile%20%28without%20patch%29/logs/stdio
FAILED: alternate_version_generator.exe 
E:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /OUT:alternate_version_generator.exe /PDB:alternate_version_generator.exe.pdb @alternate_version_generator.exe.rsp
LINK : fatal error LNK1207: incompatible PDB format in 'E:\b\build\slave\win_clang\build\src\out\Debug_x64\alternate_version_generator.exe.pdb'; delete and rebuild
FAILED: upgrade_test.exe 
E:/b/depot_tools/python276_bin/python.exe gyp-win-tool link-wrapper environment.x64 False link.exe /nologo /OUT:upgrade_test.exe /PDB:upgrade_test.exe.pdb @upgrade_test.exe.rsp
LINK : fatal error LNK1207: incompatible PDB format in 'E:\b\build\slave\win_clang\build\src\out\Debug_x64\upgrade_test.exe.pdb'; delete and rebuild




We didn't see this until recently, so this is probably triggered by incremental linking too (?)

Comment 1 by thakis@chromium.org, May 9 2016 

Hm, maybe this happens when switching between incremental and non-incremental linking, and this'll fix itself either when deleting these files or when doing a clobber build?

But then again, we did a clang roll on Saturday which should've caused a full rebuild. Maybe due to /INCREMENTAL rebuilding every .obj isn't a real full rebuild?

Comment 2 by thakis@chromium.org, May 10 2016

Cc: scottmg@chromium.org
It feels like this is happening way less frequently today. Maybe it's some transient thing caused by us switching on /INCREMENTAL again.

scottmg, do you remember if switching between /INCREMENTAL and non-incremental links required clobber builds on the normal win bots back when it got enabled?

Comment 3 by scottmg@chromium.org, May 10 2016 

No, I've never seen that before related to incremental, only between major revs of VS.

Comment 4 by r...@chromium.org, May 10 2016 

Those bots are also building with fastbuild=1, meaning clang shouldn't be generating any CodeView. I don't know what could be causing this on the compiler side.

Comment 5 by thakis@chromium.org, May 26 2016 

This still happens in about 1% of builds. I'm currently seeing this on https://build.chromium.org/p/tryserver.chromium.win/buildslaves/vm831-m4 (where it happens reliably) and https://build.chromium.org/p/tryserver.chromium.win/buildslaves/vm622-m4 . Maybe these two slaves just needs clobbers. Will keep monitoring.

Comment 7 by thakis@chromium.org, Oct 25 2016

Status: WontFix (was: Untriaged)
I haven't seen this in a long time. I just went through all red builds in win_clang's last 200 builds and haven't seen it there. I think this went away.

Comment 8 by r...@chromium.org, Oct 25 2016 

I think this was fixed for good in r280522 from early September.
►

Sign in to add a comment