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

Failed Build #14721 (Sep 18, 2019 12:36:19 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372200
  • http://llvm.org/svn/llvm-project/cfe/trunk : 372197
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 372143
  • http://llvm.org/svn/llvm-project/zorg/trunk : 371835
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 372034
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 372128
Changes
  1. [X86] Break non-power of 2 vXi1 vectors into scalars for argument passing with avx512.

    This generates worse code, but matches what is done for avx2 and
    prevents crashes when more arguments are passed than we have
    registers for. (detail)
    by ctopper
  2. [X86] Add test case for passing a v17i1 vector with avx512 (detail)
    by ctopper
  3. [BPF] Permit all user instructed offset relocatiions

    Currently, not all user specified relocations
    (with clang intrinsic __builtin_preserve_access_index())
    will turn into relocations.

    In the current implementation, a __builtin_preserve_access_index()
    chain is turned into relocation only if the result of the clang
    intrinsic is used in a function call or a nonzero offset computation
    of getelementptr. For all other cases, the relocatiion request
    is ignored and the __builtin_preserve_access_index() is turned
    into regular getelementptr instructions.
    The main reason is to mimic bpf_probe_read() requirement.

    But there are other use cases where relocatable offset is
    generated but not used for bpf_probe_read(). This patch
    relaxed previous constraints when to generate relocations.
    Now, all user __builtin_preserve_access_index() will have
    relocations generated.

    Differential Revision: https://reviews.llvm.org/D67688 (detail)
    by yhs

Started by timer (4 times)

This run spent:

  • 3 hr 25 min waiting;
  • 4 hr 10 min build duration;
  • 7 hr 36 min total from scheduled to completion.

Identified problems

Missing test results

The test result file Jenkins is looking for does not exist after the build.
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

Ninja target failed

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