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

Failed Build #14868 (Oct 11, 2019 7:20:53 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 374623
  • 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/zorg/trunk : 374594
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 374510
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 374551
Changes
  1. [asan] Return true from instrumentModule

    createSanitizerCtorAndInitFunctions always change the module. (detail)
    by Vitaly Buka
  2. DebugInfo: Fix msan use-of-uninitialized exposed by r374600 (detail)
    by dblaikie
  3. [llvm-profdata] Make "malformed-ptr-to-counter-array.test" textual

    As pointed out in https://reviews.llvm.org/D66979 post-commit, making
    this test textual would make it more maintainable.

    Differential Revision: https://reviews.llvm.org/D68718 (detail)
    by Vedant Kumar
  4. [X86] Fold a VTRUNCS/VTRUNCUS+store into a saturating truncating store.

    We already did this for VTRUNCUS with a specific combination of
    types. This extends this to VTRUNCS and handles any types where
    a truncating store is legal. (detail)
    by ctopper
  5. [X86] Add test case showing missing opportunity to fold vmovsdb into a store after type legalization. NFC (detail)
    by ctopper
  6. DebugInfo: Reduce the scope of some variables related to debug_ranges emission

    Minor tidy up/NFC (detail)
    by dblaikie
  7. [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)
    by jakehehrlich
  8. gn build: (manually) merge r374606 better (detail)
    by nico
  9. gn build: Merge r235758 (detail)
    by gnsyncbot
  10. gn build: Cmanually) merge r374590 (detail)
    by nico
  11. [AMDGPU] Use GCN prefix in dpp_combine.mir. NFC. (detail)
    by rampitec
  12. [AMDGPU] link dpp pseudos and real instructions on gfx10

    This defaults to zero fi operand, but we do not expose it
    anyway. Should we expose it later it needs to be added to
    the pseudo.

    This enables dpp combining on gfx10.

    Differential Revision: https://reviews.llvm.org/D68888 (detail)
    by rampitec
  13. [lit] Small cleanups in main.py

    * Extract separate function for running tests from main
    * Push single-usage imports to point of usage
    * Remove unnecessary sys.exit(0) calls

    Reviewed By: rnk

    Differential Revision: https://reviews.llvm.org/D68836 (detail)
    by yln
  14. [lit] Change regex filter to ignore case

    Make regex filter `--filter=REGEX` option more lenient via
    `re.IGNORECASE`.

    Reviewed By: yln

    Differential Revision: https://reviews.llvm.org/D68834 (detail)
    by yln
  15. DebugInfo: Use base address selection entries for debug_loc

    Unify the range and loc emission (for both DWARFv4 and DWARFv5 style lists) and take advantage of that unification to use strategic base addresses for loclists.

    Differential Revision: https://reviews.llvm.org/D68620 (detail)
    by dblaikie

Started by timer (5 times)

This run spent:

  • 4 hr 10 min waiting;
  • 4 hr 20 min build duration;
  • 8 hr 31 min total from scheduled to completion.

Identified problems

Ninja target failed

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

Missing test results

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

Regression test failed

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