Started 8 mo 21 days ago
Took 2 hr 38 min on green-dragon-16

Failed Build rL:372198 - C:372197 - #649 (Sep 17, 2019 9:03:58 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372198
  • 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/debuginfo-tests/trunk : 364589
  • 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. [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/ViewSVN)
    by yhs

Started by an SCM change

This run spent:

  • 12 min waiting;
  • 2 hr 38 min build duration;
  • 2 hr 50 min total from scheduled to completion.
LLVM/Clang Warnings: 2 warnings.

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

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

Regression test failed

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

Ninja target failed

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