Started 2 yr 4 mo ago
Took 2 hr 17 min on green-dragon-14

Failed Build #120 (Oct 9, 2017 2:12:25 PM)

Revisions
  • http://llvm.org/svn/llvm-project/clang-tools-extra/branches/release_50 : 315224
  • http://llvm.org/svn/llvm-project/libcxx/branches/release_50 : 311735
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 313634
  • http://llvm.org/svn/llvm-project/zorg/trunk : 315233
  • http://llvm.org/svn/llvm-project/llvm/branches/release_50 : 315198
  • http://llvm.org/svn/llvm-project/compiler-rt/branches/release_50 : 311736
  • http://llvm.org/svn/llvm-project/cfe/branches/release_50 : 314569
Changes
  1. Disabled warnings escalation on Windows buildbots when built by VS.

    Because of the bug in the MS compiler we disable the warnings escalation for now on Windows buildbots. See https://connect.microsoft.com/VisualStudio/feedback/details/668639/c-c4709-when-not-even-using-comma-inside-the-array-index-expression-w4 for more details. (detail)
    by gkistanova
  2. Merging r309979:

    ------------------------------------------------------------------------
    r309979 | mgorny | 2017-08-03 12:41:33 -0700 (Thu, 03 Aug 2017) | 16 lines

    [test] Fix clang library dir in LD_LIBRARY_PATH For stand-alone build

    Prepend the clang library directory (determined using SHLIBDIR, alike
    in clang) to the LD_LIBRARY_PATH to ensure that just-built clang
    libraries will be used instead of a previous installed version.

    When a stand-alone build is performed, LLVM_LIBS_DIR contains the path
    to installed LLVM library directory. The same directory frequently
    contains a previously installed version of clang. SHLIBDIR, on the other
    hand, is always the build-tree directory, and therefore contains
    the freshly built clang libraries.

    In a non-stand-alone build, both paths will be the same and therefore
    including them both will not cause any issues.

    Differential Revision: https://reviews.llvm.org/D30155
    ------------------------------------------------------------------------ (detail)
    by tstellar

Started by an SCM change (2 times)

This run spent:

  • 3 hr 5 min waiting;
  • 2 hr 17 min build duration;
  • 5 hr 23 min total from scheduled to completion.
Test Result (1 failure / ±0)

Identified problems

Regression test failed

This build failed because a regression test in the test suite FAILed. See the test report for details.
Indication 1

Compile Error

This build failed because of a compile error. Below is a list of all errors in the build log:
Indication 2

Ninja target failed

Below is a link to the first failed ninja target.
Indication 3