Started 27 days ago
Took 5 hr 8 min on green-dragon-02

Failed Build #14911 (Oct 19, 2019 4:33:31 AM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 375339
  • http://llvm.org/svn/llvm-project/cfe/trunk : 375338
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 375317
  • http://llvm.org/svn/llvm-project/zorg/trunk : 375336
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 375340
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 375316
Changes
  1. Refine check for `_LIBCPP_C_HAS_NO_GETS` on FreeBSD

    Summary:
    In D67316 we added `_LIBCPP_C_HAS_NO_GETS` to signal that the C library
    does not provide `gets()`, and added a test for FreeBSD 13 or higher,
    using the compiler-defined `__FreeBSD__` macro.

    Unfortunately this did not work that well for FreeBSD's own CI process,
    since the gcc compilers used for some architectures define `__FreeBSD__`
    to match the build host, not the target.

    Instead, we should use the `__FreeBSD_version` macro from the userland
    header `<osreldate.h>`, which is more fine-grained.  See also
    <https://reviews.freebsd.org/D22034>.

    Reviewers: EricWF, mclow.lists, emaste, ldionne

    Reviewed By: emaste, ldionne

    Subscribers: dexonsmith, bsdjhb, krytarowski, christof, ldionne, libcxx-commits

    Differential Revision: https://reviews.llvm.org/D69174 (detail)
    by dim
  2. Explicit in the doc the current list of projects (with easy copy and paste) (detail)
    by sylvestre
  3. Revert "[Implicit Modules] Add -cc1 option -fmodules-strict-context-hash which includes search paths and diagnostics." and "[Docs] Fix header level."

    The test doesn't work on Windows. I'll fix it and recommit later. (detail)
    by mspencer
  4. Make it clear in the doc that 'all' in LLVM_ENABLE_PROJECTS does install ALL projects (detail)
    by sylvestre
  5. Handle is_legacy_mode in LLDPerformanceTestsuite. (detail)
    by gkistanova

Started by timer (5 times)

This run spent:

  • 4 hr 22 min waiting;
  • 5 hr 8 min build duration;
  • 9 hr 31 min total from scheduled to completion.

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

Missing test results

The test result file Jenkins is looking for does not exist after the build.
Indication 3