Started 2 mo 18 days ago
Took 1 hr 2 min on green-dragon-19

Failed Build rL:372529 - C:372527 - #725 (Sep 22, 2019 2:21:15 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372529
  • http://llvm.org/svn/llvm-project/cfe/trunk : 372527
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 372511
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/zorg/trunk : 372433
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 372242
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 372445
Changes
  1. Verifier - silence static analyzer dyn_cast<VectorType> null dereference warnings. NFCI.

    The static analyzer is warning about potential null dereferences, but we should be able to use cast<VectorType> directly and if not assert will fire for us. (detail/ViewSVN)
    by rksimon
  2. [AMDGPU] isSDNodeAlwaysUniform - silence static analyzer dyn_cast<LoadSDNode> null dereference warning. NFCI.

    The static analyzer is warning about a potential null dereference, but we should be able to use cast<LoadSDNode> directly and if not assert will fire for us. (detail/ViewSVN)
    by rksimon
  3. [clang] [Basic] Enable __has_feature(leak_sanitizer)

    Add a 'leak_sanitizer' feature akin to existing '*_sanitizer' features
    to let programmers switch code paths accounting for leak sanitizers
    being enabled.

    Differential Revision: https://reviews.llvm.org/D67719 (detail/ViewSVN)
    by mgorny
  4. [X86] Fix some VCVTPS2PH isel patterns where 'i32' was used instead of 'timm'

    This seems to have completed omitted any check for the opcode
    of the operand in the isel table. (detail/ViewSVN)
    by ctopper

Started by an SCM change (3 times)

This run spent:

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

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

Assertion failure

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

Regression test failed

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

Missing test results

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