Started 26 days ago
Took 4 hr 13 min on green-dragon-02

Failed Build #14735 (Sep 20, 2019 7:32:20 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372395
  • http://llvm.org/svn/llvm-project/cfe/trunk : 372394
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 372348
  • http://llvm.org/svn/llvm-project/zorg/trunk : 372342
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 372242
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 372388
Changes
  1. Use llvm::StringLiteral instead of StringRef in few places (detail)
    by maskray
  2. [CUDA][HIP] Fix hostness of defaulted constructor
    Clang does not respect the explicit device host attributes of defaulted special members.
    Also clang does not respect the hostness of special members determined by their
    first declarations.
    Clang also adds duplicate implicit device or host attributes in certain cases.
    This patch fixes that.
    Differential Revision: https://reviews.llvm.org/D67509 (detail)
    by yaxunl
  3. [SLPVectorizer] add tests for bogus reductions; NFC

    https://bugs.llvm.org/show_bug.cgi?id=42708
    https://bugs.llvm.org/show_bug.cgi?id=43146 (detail)
    by spatel
  4. [Testing] Python 3 requires `print` to use parens (detail)
    by davezarzycki
  5. [RISCV] Fix static analysis issues

    Unlikely to be problematic but still worth fixing.

    Differential Revision: https://reviews.llvm.org/D67640 (detail)
    by luismarques
  6. [Alignment][NFC] migrate DataLayout internal struct to llvm::Align

    Summary:
    This is patch is part of a series to introduce an Alignment type.
    See this thread for context: http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html
    See this patch for the introduction of the type: https://reviews.llvm.org/D64790

    With this patch the PointerAlignElem struct goes from 20B to 16B.

    Reviewers: courbet

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D67400 (detail)
    by gchatelet
  7. [FastISel] Fix insertion of unconditional branches during FastISel

    The insertion of an unconditional branch during FastISel can differ depending on
    building with or without debug information. This happens because FastISel::fastEmitBranch
    emits an unconditional branch depending on the size of the current basic block
    without distinguishing between debug and non-debug instructions.

    This patch fixes this issue by ignoring debug instructions when getting the size
    of the basic block.

    Reviewers: aprantl

    Reviewed By: aprantl

    Subscribers: ormris, aprantl, hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D67703 (detail)
    by tellenbach
  8. [clang-tidy] Fix relative path in header-filter.

    Summary:
    Clang-tidy supports output diagnostics from header files if user
    specifies --header-filter. But it can't handle relative path well.
    For example, the folder structure of a project is:

    ```
    // a.h is in /src/a/a.h

    // b.h is in /src/b/b.h
    ...

    // c.cpp is in /src/c.cpp

    ```

    Now, we set --header-filter as --header-filter=/a/. That means we only
    want to check header files under /src/a/ path, and ignore header files
    uder /src/b/ path, but in current implementation, clang-tidy will check
    /src/b/b.h also, because the name of b.h used in clang-tidy is
    /src/a/../b/b.h.

    This change tries to fix this issue.

    Reviewers: alexfh, hokein, aaron.ballman, gribozavr

    Reviewed By: gribozavr

    Subscribers: MyDeveloperDay, xazax.hun, cfe-commits

    Tags: #clang, #clang-tools-extra

    Differential Revision: https://reviews.llvm.org/D67501

    Patch by Yubo Xie. (detail)
    by gribozavr
  9. [SystemZ]  Add SystemZ as supporting target in help text for -mfentry.

    => "Insert calls to fentry at function entry (x86/SystemZ only)"

    Review: Ulrich Weigand (detail)
    by jonpa
  10. [StaticAnalyzer] Use llvm::StringLiteral instead of StringRef in few places

    StringRef's constexpr constructor seems to be extremely slow in MSVC
    2017, so don't use it for generated tables. Should make PR43369 a bit
    better, no functionality change. (detail)
    by d0k
  11. [AMDGPU] Use std::make_tuple to make some toolchains happy again

    My toolchain stopped working (LLVM 8.0 , libstdc++ 5.4.0) after
    r372338.

    The same problem was seen in clang-cuda-build buildbots:

    clang-cuda-build/llvm/lib/Target/AMDGPU/AMDGPUInstructionSelector.cpp:763:12:
    error: chosen constructor is explicit in copy-initialization
        return {Reg, 0, nullptr};
               ^~~~~~~~~~~~~~~~~
    /usr/bin/../lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/tuple:479:19:
    note: explicit constructor declared here
            constexpr tuple(_UElements&&... __elements)
                      ^

    This commit adds explicit calls to std::make_tuple to work around
    the problem. (detail)
    by bjope
  12. Revert r372366 "Use getTargetConstant for BLENDI, and add a test to catch it."

    This reverts commit 52621307bcab2013e8833f3317cebd63a6db3885.

    Tests have been failing all night with

        [0/2] ACTION //llvm/test:check-llvm(//llvm/utils/gn/build/toolchain:unix)
        -- Testing: 33647 tests, 64 threads --
        Testing: 0 .. 10..
        UNRESOLVED: LLVM :: CodeGen/AMDGPU/GlobalISel/isel-blendi-gettargetconstant.ll (6943 of 33647)
        ******************** TEST 'LLVM :: CodeGen/AMDGPU/GlobalISel/isel-blendi-gettargetconstant.ll' FAILED ********************
        Test has no run line!
        ********************

    Since there were other concerns on https://reviews.llvm.org/D67785,
    I'm just reverting for now. (detail)
    by nico

Started by timer (5 times)

This run spent:

  • 4 hr 21 min waiting;
  • 4 hr 13 min build duration;
  • 8 hr 34 min total from scheduled to completion.

Identified problems

Ninja target failed

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

Regression test failed

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

Missing test results

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