Started 9 days 2 hr ago
Took 10 min on green-dragon-08

Failed Build #5515 (Oct 11, 2019 4:53:34 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 374613
  • http://llvm.org/svn/llvm-project/cfe/trunk : 374596
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 374612
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 374510
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 374551
Changes
  1. DebugInfo: Reduce the scope of some variables related to debug_ranges emission

    Minor tidy up/NFC (detail/ViewSVN)
    by dblaikie
  2. [libFuzzer] Don't prefix absolute paths in fuchsia.

    The ExecuteCommand function in fuchsia used to prefix the
    getOutputFile for each command run with the artifact_prefix flag if
    it was available, because fuchsia components don't have a writable working
    directory. However, if a file with a global path is provided, fuchsia
    should honor that.

    An example of this is using the global /tmp directory to store stuff.
    In fuchsia it ended up being translated to data///tmp, whereas we want
    to make sure it is using /tmp (which is available to components using the
    isolated-temp feature).

    To test this I made the change, compiled fuchsia with this toolchain and
    ran a fuzzer with the -fork=1 flag (that mode makes use of the /tmp
    directory). I also tested that normal fuzzing workflow was not affected
    by this.

    Author: charco (Marco Vanotti)
    Differential Revision: https://reviews.llvm.org/D68774 (detail/ViewSVN)
    by jakehehrlich
  3. gn build: (manually) merge r374606 better (detail/ViewSVN)
    by nico
  4. gn build: Merge r235758 (detail/ViewSVN)
    by gnsyncbot
  5. gn build: Cmanually) merge r374590 (detail/ViewSVN)
    by nico

Started by upstream project Clang Stage 2: cmake, R -g Tsan, using Stage 1 RA build number 18484
originally caused by:

This run spent:

  • 7 sec waiting;
  • 10 min build duration;
  • 10 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