Started 12 days ago
Took 1 hr 54 min on green-dragon-22

Failed Build #18406 (Jul 8, 2019 8:14:47 AM)

  • : 365320
  • : 365315
  • : 365307
  • : 364589
  • : 365290
  • : 365311
  1. GlobalISel: widenScalar for G_BUILD_VECTOR (detail/ViewSVN)
    by arsenm
  2. GlobalISel: Check address space when looking up iPTR size

    Fixes AMDGPU patterns for 32-bit address spaces always failing. Tests
    will be included in future patches when additional issues are solved. (detail/ViewSVN)
    by arsenm
  3. Reapply [llvm-ar][test] Increase llvm-ar test coverage

    This change adds tests to cover existing llvm-ar functionality.

    Differential Revision: (detail/ViewSVN)
    by gbreynoo
  4. Revert [llvm-ar][test] Increase llvm-ar test coverage

    Reverted due to test failures

    Differential Revision: (detail/ViewSVN)
    by gbreynoo
  5. [llvm-ar][test] Increase llvm-ar test coverage

    This change adds tests to cover existing llvm-ar functionality.

    Differential Revision: (detail/ViewSVN)
    by gbreynoo
  6. [ASTImporter] Fix import of lambda in function param

    The current import implementation fails to import the definition of a
    lambda class if the lambda class is defined in a function param.
    E.g., the lambda class below will be imported without any methods:
      template <typename F>
      void f(F L = [](){}) {}

    Reviewers: a_sidorin, a.sidorin, shafik

    Subscribers: rnkovacs, dkrupp, Szelethus, gamesh411, cfe-commits

    Tags: #clang

    Differential Revision: (detail/ViewSVN)
    by martong
  7. [analyzer] Add analyzer option to limit the number of imported TUs

    During CTU analysis of complex projects, the loaded AST-contents of
    imported TUs can grow bigger than available system memory. This option
    introduces a threshold on the number of TUs to be imported for a single
    TU in order to prevent such cases.

    Differential Revision: (detail/ViewSVN)
    by gamesh411
  8. [lit] Parse command-line options from LIT_OPTS

    Similar to `FILECHECK_OPTS` for FileCheck, `LIT_OPTS` makes it easy to
    adjust lit behavior when running the test suite via ninja.  For

    $ LIT_OPTS='--time-tests -vv --filter=threadprivate' \
      ninja check-clang-openmp

    Reviewed By: probinson

    Differential Revision: (detail/ViewSVN)
    by jdenny
  9. [docs][llvm-objcopy] Add description of binary input/output to doc

    We briefly referred to being able to specify --target=binary without
    explaining what binary input/output meant. This change adds a section on

    Reviewed by: MaskRay, abrachet

    Differential Revision: (detail/ViewSVN)
    by jhenderson
  10. [clangd] Use xxhash instead of SHA1 for background index file digests.

    Currently SHA1 is about 10% of our CPU, this patch reduces it to ~1%.

    xxhash is a well-defined (stable) non-cryptographic hash optimized for
    fast checksums (like crc32).
    Collisions shouldn't be a problem, despite the reduced length:
    - for actual file content (used to invalidate bg index shards), there
       are only two versions that can collide (new shard and old shard).
    - for file paths in bg index shard filenames, we would need 2^32 files
       with the same filename to expect a collision. Imperfect hashing may
       reduce this a bit but it's well beyond what's plausible.

    This will invalidate shards on disk (as usual; I bumped the version),
    but this time the filenames are changing so the old files will stick
    around :-( So this is more expensive than the usual bump, but would be
    good to land before the v9 branch when everyone will start using bg index.

    Reviewers: kadircet

    Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, llvm-commits

    Tags: #llvm

    Differential Revision: (detail/ViewSVN)
    by sammccall

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

This run spent:

  • 2 ms waiting;
  • 1 hr 54 min build duration;
  • 1 hr 54 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