Enable asserts on llvm-next waterfall builders |
|||
Issue descriptionMore testing is required for llvm-next builds. The clang error reported in https://bugs.chromium.org/p/chromium/issues/detail?id=690639 would have been caught early if llvm was build with asserts enabled.
,
Feb 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/aaba78ccd1585b0a712f30d7877e6835625dd25c commit aaba78ccd1585b0a712f30d7877e6835625dd25c Author: Manoj Gupta <manojgupta@google.com> Date: Fri Feb 24 23:30:47 2017 Enable asserts on llvm-next build. Enabling asserts should help catch more errors for llvm-next builders. BUG= chromium:694804 TEST=Building sys-libs/pam fails for veyron_jaq with llvm-next. Change-Id: Iab6775823cce5b87ce89f5ed33aee0541f848b09 Reviewed-on: https://chromium-review.googlesource.com/445865 Commit-Queue: Manoj Gupta <manojgupta@chromium.org> Tested-by: Manoj Gupta <manojgupta@chromium.org> Trybot-Ready: Manoj Gupta <manojgupta@chromium.org> Reviewed-by: Ting-Yuan Huang <laszio@chromium.org> [rename] https://crrev.com/aaba78ccd1585b0a712f30d7877e6835625dd25c/sys-devel/llvm/llvm-4.0_pre285905-r6.ebuild
,
Feb 24 2017
,
Mar 17 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by bugdroid1@chromium.org
, Feb 24 2017