Started 7 days 18 hr ago
Took 1 hr 13 min on green-dragon-20

Failed Build rL:371523 - C:371522 - #533 (Sep 10, 2019 7:21:36 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 371523
  • http://llvm.org/svn/llvm-project/cfe/trunk : 371522
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 371453
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/zorg/trunk : 371154
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 371324
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 371504
Changes
  1. [VectorUtils] Remove unused include. [NFC]

    Patch by Francesco Petrogalli <francesco.petrogalli@arm.com>

    Reviewers: fhahn

    Reviewed By: fhahn

    Differential Revision: https://reviews.llvm.org/D67365 (detail/ViewSVN)
    by fhahn
  2. [clang][codegen][NFC] Make test patterns more permissive.

    See the discussion in:
    http://lists.llvm.org/pipermail/llvm-commits/Week-of-Mon-20190909/692736.html (detail/ViewSVN)
    by courbet
  3. [CMake] Don't pass all LLVM_COMPILE_FLAGS to the C compiler

    GCC (unlike clang!) warns about C++ flags when compiling C.

    https://reviews.llvm.org/D67171 (detail/ViewSVN)
    by davezarzycki
  4. [utils] Implement the llvm-locstats tool

    The tool reports verbose output for the DWARF debug location coverage.
    The llvm-locstats for each variable or formal parameter DIE computes what
    percentage from the code section bytes, where it is in scope, it has
    location description. The line 0 shows the number (and the percentage) of
    DIEs with no location information, but the line 100 shows the number (and
    the percentage) of DIEs where there is location information in all code
    section bytes (where the variable or parameter is in the scope). The line
    50..59 shows the number (and the percentage) of DIEs where the location
    information is in between 50 and 59 percentage of its scope covered.

    The tool will be very useful for tracking improvements regarding the
    "debugging optimized code" support with LLVM ecosystem.

    Differential Revision: https://reviews.llvm.org/D66526 (detail/ViewSVN)
    by djtodoro

Started by an SCM change (2 times)

This run spent:

  • 29 min waiting;
  • 1 hr 13 min build duration;
  • 1 hr 43 min total from scheduled to completion.
LLVM/Clang Warnings: 2 warnings.

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

Assertion failure

This build failed because of an assertion failure. Below is a list of all errors in the build log:
Indication 3

Ninja target failed

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

Missing test results

The test result file Jenkins is looking for does not exist after the build.
Indication 5