Started 4 days 7 hr ago
Took 10 min on green-dragon-08

Failed Build #5513 (Oct 11, 2019 2:56:16 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 374602
  • http://llvm.org/svn/llvm-project/cfe/trunk : 374596
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 374472
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 374510
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 374551
Changes
  1. [lit] Small cleanups in main.py

    * Extract separate function for running tests from main
    * Push single-usage imports to point of usage
    * Remove unnecessary sys.exit(0) calls

    Reviewed By: rnk

    Differential Revision: https://reviews.llvm.org/D68836 (detail/ViewSVN)
    by yln
  2. [lit] Change regex filter to ignore case

    Make regex filter `--filter=REGEX` option more lenient via
    `re.IGNORECASE`.

    Reviewed By: yln

    Differential Revision: https://reviews.llvm.org/D68834 (detail/ViewSVN)
    by yln
  3. DebugInfo: Use base address selection entries for debug_loc

    Unify the range and loc emission (for both DWARFv4 and DWARFv5 style lists) and take advantage of that unification to use strategic base addresses for loclists.

    Differential Revision: https://reviews.llvm.org/D68620 (detail/ViewSVN)
    by dblaikie
  4. [mips] Remove unused local variables. NFC (detail/ViewSVN)
    by atanasyan
  5. [mips] Store 64-bit `li.d' operand as a single 8-byte value

    Now assembler generates two consecutive `.4byte` directives to store
    64-bit `li.d' operand. The first directive stores high 4-byte of the
    value. The second directive stores low 4-byte of the value. But on
    64-bit system we load this value at once and get wrong result if the
    system is little-endian.

    This patch fixes the bug. It stores the `li.d' operand as a single
    8-byte value.

    Differential Revision: https://reviews.llvm.org/D68778 (detail/ViewSVN)
    by atanasyan
  6. [mips] Use less instruction to load zero into FPR by li.s / li.d pseudos

    If `li.s` or `li.d` loads zero into a FPR, it's not necessary to load
    zero into `at` GPR register and then move its value into a floating
    point register. We can use as a source register the `zero / $0` one.

    Differential Revision: https://reviews.llvm.org/D68777 (detail/ViewSVN)
    by atanasyan
  7. [ObjC] Remove default parameter no caller was providing. NFC intended.

    Currently there is no need to make ObjCTypeParamType have a canonical type
    different from the one in corresponding ObjCTypeParamDecl. So remove the
    corresponding unused API. (detail/ViewSVN)
    by vsapsai
  8. [GISel][UnitTest] Fix a bunch of tests that were not doing anything

    After r368065, all the tests using GISelMITest must call setUp() before
    doing anything, otherwise the TargetMachine is not going to be set up.
    A few tests added after that commit were not doing that and ended up
    testing effectively nothing.

    Fix the setup of all the tests and fix the failing tests. (detail/ViewSVN)
    by qcolombet

Started by upstream project Clang Stage 2: cmake, R -g Tsan, using Stage 1 RA build number 18482
originally caused by:

This run spent:

  • 7.2 sec waiting;
  • 10 min build duration;
  • 10 min total from scheduled to completion.

Identified problems

Ninja target failed

Below is a link to the first failed ninja target.
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

Missing test results

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