Started 1 mo 0 days ago
Took 4 hr 9 min on green-dragon-02

Failed Build #14713 (Sep 16, 2019 7:17:18 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372054
  • http://llvm.org/svn/llvm-project/cfe/trunk : 372058
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 372056
  • 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 : 372037
Changes
  1. Push lambda scope earlier when transforming lambda expression

    Differential Revision: https://reviews.llvm.org/D66067 (detail)
    by comex
  2. [libFuzzer] Always print DSO map on Fuchsia libFuzzer launch

    Fuchsia doesn't have /proc/id/maps, so it relies on the kernel logging system
    to provide the DSO map to be able to symbolize in the context of ASLR. The DSO
    map is logged automatically on Fuchsia when encountering a crash or writing to
    the sanitizer log for the first time in a process. There are several cases
    where libFuzzer doesn't encounter a crash, e.g. on timeouts, OOMs, and when
    configured to print new PCs as they become covered, to name a few. Therefore,
    this change always writes to the sanitizer log on startup to ensure the DSO map
    is available in the log.

    Author: aarongreen
    Differential Revision: https://reviews.llvm.org/D66233 (detail)
    by jakehehrlich
  3. [OPENMP] Fix the test, NFC (detail)
    by abataev
  4. llvm-reduce: Clean out previous test temp/output dir, since it was a dir and now it's used as just a single file (detail)
    by dblaikie
  5. llvm-reduce: Remove some string copies (detail)
    by dblaikie
  6. Revert r372035: "[lit] Make internal diff work in pipelines"

    This breaks a Windows bot. (detail)
    by jdenny
  7. [GlobalISel] Partially revert r371901.

    r371901 was overeager and widenScalarDst() and the like in the legalizer
    attempt to increment the insert point given in order to add new instructions
    after the currently legalizing inst. In cases where the insertion point is not
    exactly the current instruction, then callers need to de-compensate for the
    behaviour by decrementing the insertion iterator before calling them. It's not
    a nice state of affairs, for now just undo the problematic parts of the change. (detail)
    by aemerson
  8. llvm-reduce: Make tests shell-independent by passing the interpreter on the command line rather than using #! in the test file (detail)
    by dblaikie
  9. Add libc to path mappings in git-llvm. (detail)
    by dlj
  10. [PowerPC] Cust lower fpext v2f32 to v2f64 from extract_subvector v4f32

    Add the missing piece of r372029.
    Somehow when the patch for review D61961 was committed, only the test case
    went in and the code didn't. This of course caused all kinds of build bot
    breaks.
    This patch just adds the code for that patch.

    Author: Lei Huang
    Differential revision: https://reviews.llvm.org/D61961 (detail)
    by nemanjai
  11. [Remarks] Allow remarks::Format::YAML to take a string table

    It should be allowed to take a string table in case all the strings in
    the remarks point there, but it shouldn't use it during serialization. (detail)
    by thegameg
  12. [test] Clean up previous raw profile before merging into it

    This fixes a test failure in instrprof-set-file-object-merging.c which
    seems to have been caused by reuse of stale data in old raw profiles. (detail)
    by Vedant Kumar
  13. [OPENMP]Fix the test, NFC. (detail)
    by abataev

Started by timer (4 times)

This run spent:

  • 3 hr 6 min waiting;
  • 4 hr 9 min build duration;
  • 7 hr 16 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

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