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

Issue 618838 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

building w/ msan on linux is really really slow locally

Project Member Reported by dpranke@chromium.org, Jun 9 2016

Issue description

I'm working on getting the last MSAN builders flipped over to GN, and building browser_tests locally on my z600 is really really slow for both GN and GYP. I'm seemingly seeing one second per translation unit for most (but not all) files. I'm using goma but I'm not sure if that's helping or hurting.


I'm using 

GYP_DEFINES='clang=1 use_goma=1 component=static_library dcheck_always_on=1 fastbuild=1 msan=1 msan_track_origins=2 test_isolation_mode=prepare use_prebuilt_instrumented_libraries=1' 

and gn args:

dcheck_always_on = true
is_component_build = false
is_debug = false
is_msan = true
msan_track_origins = 2
symbol_level = 1
use_goma = true
use_prebuilt_instrumented_libraries = true

I had earlier done a tip-of-tree llvm build in this checkout (LLVM_FORCE_HEAD_REVISION=1) and I'm wondering if that caused the toolchains to get mixed up or something.

I just rebooted my machine, clobbered my build directory, deleted third_party/llvm-build/cr_build_revision, re-ran tools/clangs/scripts/update.py and am now trying again. 

I'm synced to r398686 ...
 
sounds like you used a locally-built clang that happens to disable goma. Is it better now? Are most finished tasks on localhost:8088 green now?
Status: WontFix (was: Untriaged)
yeah. I think resetting the toolchain fixed things. Thanks!

Sign in to add a comment