ASAN and TSAN Debug build failure |
||||||
Issue descriptionhttps://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.lkgr%2FASAN_Debug%2F8118%2F%2B%2Frecipes%2Fsteps%2Fcompile%2F0%2Fstdout https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.lkgr%2FTSAN_Debug%2F6446%2F%2B%2Frecipes%2Fsteps%2Fcompile%2F0%2Fstdout Seem to be coming from recent changes by Martijin@. Ryan, can you please take a look.
,
Apr 10 2017
Do we need to R-V-G this? Marijin's change doesn't look right to me, I'd appreciate if Brett could view it. It seems related to the GN bits, perhaps with how tools are built. I'm going to ask that Brett take a look at this, but perhaps it's related to Recipes and/or the recent sysroot change. Do we need to revert? e.g. is this a tree closer bot? (I thought 'lkgr' was 'FYI - bot owners maintain it' at this point).
,
Apr 10 2017
No need to RVG. LKGR is not a tree closer bot. Wonder if this showed on clang non-sanitizer bots. Do you know which commit is it and can be reverted.
,
Apr 10 2017
,
Apr 10 2017
https://chromium-review.googlesource.com/c/471529/ is what introduced the build-time dependency that would have triggered the tool to fail.
,
Apr 15 2017
,
Apr 15 2017
The CL that caused this was reverted earlier this week. Another CL (https://codereview.chromium.org/2808863003) should fix this problem in case the original CL relands.
,
May 22 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by mart...@martijnc.be
, Apr 10 2017