Started 6 days 18 hr ago
Took 3 hr 25 min on green-dragon-19

Failed Build #18449 (Jul 13, 2019 3:49:59 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 365997
  • http://llvm.org/svn/llvm-project/cfe/trunk : 365995
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 365982
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 365973
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 365993
Changes
  1. [Object] isNotObjectErrorInvalidFileType: simplify (detail/ViewSVN)
    by maskray
  2. [Object] isNotObjectErrorInvalidFileType: fix use-after-move (detail/ViewSVN)
    by maskray
  3. Fix -Wdocumentation warning. NFCI. (detail/ViewSVN)
    by rksimon
  4. [CMake][Fuchsia] Define asan+noexcept multilib

    Using noexcept multilib with -fno-exceptions can lead to significant
    space savings when statically linking libc++abi because we don't need
    all the unwinding and demangling code.

    When compiling with ASan, we already get a lot of overhead from the
    instrumentation itself, when statically linking libc++abi, that overhead
    is even larger.

    Having the noexcept variant for ASan can help significantly, we've seen
    more than 50% size reduction in our system image, which offsets the cost
    of having to build another multilib.

    Differential Revision: https://reviews.llvm.org/D64140 (detail/ViewSVN)
    by phosek
  5. Simplify with llvm::is_contained. NFC (detail/ViewSVN)
    by maskray
  6. This reverts commit 632a36bfcfc8273c1861f04ff6758d863c47c784.

    Some targets such as Python 2.7.16 still use VERSION in
    their builds. Without VERSION defined, the source code
    has syntax errors.

    Reverting as it will probably break many other things.

    Noticed by Sterling Augustine (detail/ViewSVN)
    by sylvestre
  7. Initialize the non-trivial C union bits I added to RecordDeclBitfields
    in r365985

    These bits weren't being initialized in the RecordDecl's constructor,
    which probably caused test/Modules/stress1.cpp to fail on a couple of
    bots. (detail/ViewSVN)
    by ahatanak
  8. [clangd] Mark type hierarchy as a supported feature in the docs

    Reviewers: sammccall

    Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, kadircet, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D64614 (detail/ViewSVN)
    by nridge
  9. [clangd] Implement typeHierarchy/resolve for subtypes

    Summary:
    This allows the client to resolve subtypes one level at a time.

    For supertypes, this is not necessary, because we eagerly compute
    supertypes and return all levels.

    Reviewers: sammccall

    Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, kadircet, cfe-commits

    Tags: #clang

    Differential Revision: https://reviews.llvm.org/D64308 (detail/ViewSVN)
    by nridge
  10. [Sema] Diagnose default-initialization, destruction, and copying of
    non-trivial C union types

    This patch diagnoses uses of non-trivial C unions and structs/unions
    containing non-trivial C unions in the following contexts, which require
    default-initialization, destruction, or copying of the union objects,
    instead of disallowing fields of non-trivial types in C unions, which is
    what we currently do:

    - function parameters.
    - function returns.
    - assignments.
    - compound literals.
    - block captures except capturing of `__block` variables by non-escaping
      blocks.
    - local and global variable definitions.
    - lvalue-to-rvalue conversions of volatile types.

    See the discussion in https://reviews.llvm.org/D62988 for more background.

    rdar://problem/50679094

    Differential Revision: https://reviews.llvm.org/D63753 (detail/ViewSVN)
    by ahatanak

Started by upstream project clang-stage2-Rthinlto_relay build number 1858
originally caused by:

This run spent:

  • 1 ms waiting;
  • 3 hr 25 min build duration;
  • 3 hr 25 min total from scheduled to completion.

Identified problems

Assertion failure

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

Ninja target failed

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

Compile Error

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

Missing test results

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