CrWinClangLLD bot is failing to link |
||
Issue descriptionFor example: https://build.chromium.org/p/chromium.fyi/builders/CrWinClangLLD/builds/5007/steps/compile/logs/stdio FAILED: app_shell_unittests.exe app_shell_unittests.exe.pdb cmd /c C:/b/depot_tools/python276_bin/python.exe ../../build/toolchain/win/tool_wrapper.py delete-file ./app_shell_unittests.exe.pdb && C:/b/depot_tools/python276_bin/python.exe ../../build/toolchain/win/tool_wrapper.py link-wrapper environment.x86 False ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo /OUT:./app_shell_unittests.exe /PDB:./app_shell_unittests.exe.pdb @./app_shell_unittests.exe.rsp Wrote crash dump file "C:\Users\CHROME~1\AppData\Local\Temp\lld-link.exe-df0d30.dmp" #0 0x0000000140b69b34 (C:\b\c\b\CrWinClangLLD\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x16f9b34) #1 0x0000000140683814 (C:\b\c\b\CrWinClangLLD\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x1213814) ... The bot has been mostly red for a while.
,
Feb 2 2017
D'oh it is. Look at me tripping over my own bot configs :-/ I don't think it's a priority making this work right now. Maybe we should turn it back to non-LTO in the meantime? And then re-purpose as a ThinTLO bot when Bob has that working?
,
Feb 2 2017
If nobody's using the bot's results atm and it's confusing, switching it back sgtm.
,
Feb 3 2017
,
Feb 3 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/3ba9c67e210df1f039f93548c1ad5bb2dfe3a945 commit 3ba9c67e210df1f039f93548c1ad5bb2dfe3a945 Author: hans <hans@chromium.org> Date: Fri Feb 03 03:43:23 2017 Turn off LTO again for Official Win/Clang LLD builds We're not working on this config at the moment, so having a red buildbot testing it is just waste of cycles. BUG= 688123 , 598772 Review-Url: https://codereview.chromium.org/2677593002 Cr-Commit-Position: refs/heads/master@{#447910} [modify] https://crrev.com/3ba9c67e210df1f039f93548c1ad5bb2dfe3a945/build/config/compiler/BUILD.gn
,
Feb 3 2017
The bot is green now. |
||
►
Sign in to add a comment |
||
Comment 1 by thakis@chromium.org
, Feb 2 2017