Started 10 days ago
Took 4 hr 52 min on green-dragon-02

Failed Build #14381 (Jul 12, 2019 9:31:11 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 365984
  • http://llvm.org/svn/llvm-project/cfe/trunk : 365989
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 365982
  • http://llvm.org/svn/llvm-project/zorg/trunk : 365596
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 365973
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 365987
Changes
  1. 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)
    by ahatanak
  2. [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)
    by nridge
  3. [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)
    by nridge
  4. [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)
    by ahatanak
  5. [Attributor][NFC] Run clang-format on the attributor files (.h/.cpp)

    The Attributor files are kept formatted with clang-format, we should try
    to keep this state. (detail)
    by jdoerfert
  6. [Attributor] Only return attributes with a valid state

    Attributor::getAAFor will now only return AbstractAttributes with a
    valid AbstractState. This simplifies call sites as they only need to
    check if the returned pointer is non-null. It also reduces the potential
    for accidental misuse. (detail)
    by jdoerfert
  7. [TSan] Tiny cleanup of UnmangleLongJmpSp for Linux/x86_64

    NFC. (detail)
    by yln
  8. clang/test/Driver/fsanitize.c: Fix -fsanitize=vptr using default target

    The default implementation of getSupportedSanitizers isn't able to turn
    on the vptr sanitizer, and thus, any platform that runs this test will
    fail with the error:

        clang: error: unsupported option '-fsanitize=vptr' for target '<target>'

    Patch by James Nagurne! (detail)
    by maskray
  9. Extend function attributes bitset size from 64 to 96.

    Summary: We are going to add a function attribute number 64.

    Reviewers: pcc, jdoerfert, lebedev.ri

    Subscribers: hiraditya, llvm-commits

    Tags: #llvm

    Differential Revision: https://reviews.llvm.org/D64663 (detail)
    by eugenis
  10. [Attributor][FIX] Lookup of (call site) argument attributes (detail)
    by jdoerfert
  11. [DirectoryWatcher][test][NFC] Add information to test failure reports (detail)
    by Jan Korous
  12. Re-land [JSONCompilationDatabase] Strip distcc/ccache/gomacc wrappers from parsed commands.

    Use //net/dir like other test cases for windows compatibility (detail)
    by sammccall
  13. PDB HashTable: Move TraitsT from class parameter to the methods that need it

    The traits object is only used by a few methods. Deserializing a hash
    table and walking it is possible without the traits object, so it
    shouldn't be required to build a dummy object for that use case.

    The TraitsT object used to be a function template parameter before
    r327647, this restores it to that state.

    This makes it clear that the traits object isn't needed at all in 1 of
    the current 3 uses of HashTable (and I am going to add another use that
    doesn't need it), and that the default PdbHashTraits isn't used outside
    of tests.

    While here, also re-enable 3 checks in the test that were commented out
    (which requires making HashTableInternals templated and giving FooBar
    an operator==).

    No intended behavior change.

    Differential Revision: https://reviews.llvm.org/D64640 (detail)
    by nico

Started by timer (5 times)

This run spent:

  • 4 hr 20 min waiting;
  • 4 hr 52 min build duration;
  • 9 hr 13 min total from scheduled to completion.
Test Result (3 failures / ±0)Show all failed tests >>>

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

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