win_xfa_clang buildbot failing |
|||||||||
Issue descriptionhttps://build.chromium.org/p/tryserver.client.pdfium/builders/win_xfa_clang on vm345-m4 has been failing. I tried a clobber build, but no luck: https://build.chromium.org/p/tryserver.client.pdfium/builders/win_xfa_clang/builds/97 [8/11] LINK_EMBED pdfium_test.exe FAILED: pdfium_test.exe pdfium_test.exe.pdb E:\b\depot_tools\python276_bin\python.exe gyp-win-tool link-with-manifests environment.x86 True pdfium_test.exe "E:\b\depot_tools\python276_bin\python.exe gyp-win-tool link-wrapper environment.x86 False link.exe /nologo /OUT:pdfium_test.exe @pdfium_test.exe.rsp" 1 mt.exe rc.exe "obj\samples\pdfium_test.pdfium_test.exe.intermediate.manifest" obj\samples\pdfium_test.pdfium_test.exe.generated.manifest LINK : fatal error LNK1285: corrupt PDB file 'E:\b\build\slave\win_xfa_clang\build\pdfium\out\Debug\pdfium_test.exe.pdb'; delete and rebuild
,
Jul 7 2016
Looks like the problem has spread to other buildbot too. https://build.chromium.org/p/client.pdfium/builders/windows_xfa_clang_x64/builds/699
,
Jul 7 2016
,
Jul 7 2016
,
Jul 7 2016
g.co/bugatrooper the priority should be zero (blocks the pdfium CQ)
,
Jul 7 2016
The following revision refers to this bug: https://pdfium.googlesource.com/pdfium.git/+/9a53675a6834d9ca82ac7b593123078de3748e11 commit 9a53675a6834d9ca82ac7b593123078de3748e11 Author: jochen <jochen@chromium.org> Date: Thu Jul 07 11:01:15 2016 Mark win_xfa_clang as experimental That way it won't block the CQ while the compile problems are being investigated. BUG= chromium:626120 NOTRY=true (otherwise, win_xfa_clang will fail and block this CL) TBR=thestig@chromium.org Review-Url: https://codereview.chromium.org/2129893002 [modify] https://crrev.com/9a53675a6834d9ca82ac7b593123078de3748e11/infra/config/cq.cfg
,
Jul 7 2016
,
Jul 7 2016
Hi, mtv trooper checking in. What can I do to help here? I see a compile failure different than the OP: subprocess.CalledProcessError: Command 'E:\b\depot_tools\python276_bin\python.exe gyp-win-tool link-wrapper environment.x86 False link.exe /nologo /OUT:mksnapshot.exe @mksnapshot.exe.rsp mksnapshot.exe.manifest.res' returned non-zero exit status 1285
,
Jul 7 2016
after I removed the bot from the CQ, it's no longer a trooper issue I think, but something someone from win/clang should look at. Nico?
,
Jul 7 2016
Got it
,
Jul 7 2016
Can we clobber the out/ directory and see if it helps? I thought I did, but my clobber build was only rebuilding ~600 targets.
,
Jul 7 2016
yesterday, I logged in to both bots and manually deleted the out/ directory. Since then, the error started to occur again on at least one of them
,
Jul 7 2016
Do you use fastbuild=1 on that bot? The chromium win/clang bots don't see that particular problem, as far as I can tell. So I'd try to get your bot to use the same compiler flags as those.
,
Jul 15 2016
+nodir@ (trooper today), I have updated the bot to GN build with symbol_level=1 (equivalent to fastbuild=1 in GYP build), could anyone/trooper login to remove the corrupted PDBs. Hopefully, no more corrupted PDB file will be generated in the future. thanks!
,
Jul 15 2016
cleaning hosts
,
Jul 15 2016
did the following ssh vm29-m3 rm -rf /cygdrive/e/b/build/slave/windows_xfa_clang* ssh vm51-m3 rm -rf /cygdrive/e/b/build/slave/windows_xfa_clang* ssh vm115-m3 rm -rf /cygdrive/e/b/build/slave/windows_xfa_clang* ssh vm119-m3 rm -rf /cygdrive/e/b/build/slave/windows_xfa_clang* ssh vm121-m3 rm -rf /cygdrive/e/b/build/slave/windows_xfa_clang* ssh vm144-m3 rm -rf /cygdrive/e/b/build/slave/windows_xfa_clang* ssh vm345-m1 rm -rf /cygdrive/e/b/build/slave/win_xfa_clan ssh vm155-m1 rm -rf /cygdrive/e/b/build/slave/win_xfa_clan
,
Jul 16 2016
thank you, Nodir. Looks like the solution is working now. Will close it. Pls reopen if the problem shows up again. thanks.
,
Aug 22 2016
,
Aug 22 2016
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by thestig@chromium.org
, Jul 7 2016