New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 669164 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

ClangToTLinuxLLD failing compile

Project Member Reported by thakis@chromium.org, Nov 28 2016

Issue description

https://build.chromium.org/p/chromium.fyi/builders/ClangToTLinuxLLD/builds/2017/steps/compile/logs/stdio

FAILED: gen/components/resources/about_credits.bro 
python ../../build/gn_run_binary.py bro --force --input gen/components/resources/about_credits.html --output gen/components/resources/about_credits.bro

Started 3 days ago, at the build above.

287924 bad, 287912 good.


svn log -r287912:287924  https://nico@llvm.org/svn/llvm-project


Maybe r287913?
 

Comment 1 by thakis@chromium.org, Nov 29 2016

Summary: ClangToTLinuxLLD failing compile (was: ClangToTLinuxLLD has failing compile)
This is still red. Rui, are you looking at this?

Comment 2 by ruiu@google.com, Nov 29 2016

I think I have to reproduce this locally to investigate as the information available from log is very few. Is this a regular build? (what is ToT?)

Comment 3 by thakis@chromium.org, Nov 29 2016

ToT means "tip of tree", that is it's just building chrome with trunk clang and lld.

Yes, it's a regular build. You can click generate_build_files's stdio at https://build.chromium.org/p/chromium.fyi/builders/ClangToTLinuxLLD/builds/2017 to find the exact args.gn the bot uses, but I'm guessing most defines will repro this. You can either set clang_base_path in your args.gn or edit toolchain.ninja to point to your locally-built lld after generating build files. Hans and Reid can help you if you get stuck.

Comment 4 by ruiu@google.com, Nov 29 2016

I succeeded to repro with a slightly older revision of lld, but interestingly it no longer crash with HEAD. I'll take a closer look into this to identify the patch that fixes it (must be a very recent commit.)

Comment 5 by ruiu@google.com, Nov 30 2016

Status: Fixed (was: Unconfirmed)
It's green now.

Comment 6 by thakis@chromium.org, Nov 30 2016

Thanks. I apologize for the badly-timed ping.

Sign in to add a comment