Started 3 days 5 hr ago
Took 4 hr 22 min on green-dragon-02

Failed Build #14869 (Oct 11, 2019 11:41:42 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 374639
  • http://llvm.org/svn/llvm-project/cfe/trunk : 374638
  • 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. [lit] Remove setting of the target-windows feature

    No other OSes use a target-<os> feature, and no tests depend on it
    any lomger.

    Differential Revision: https://reviews.llvm.org/D68450 (detail)
    by mstorsjo
  2. [clang][IFS] Fixing spelling errors in interface-stubs OPT flag (NFC).

    This is just a long standing spelling error that was found recently. (detail)
    by zer0
  3. [llvm-lipo] Pass ArrayRef by value.

    Pass ArrayRef by value, fix formatting. NFC.

    Test plan: make check-all (detail)
    by alexshap
  4. Revert 374629 "[sancov] Accommodate sancov and coverage report server for use under Windows"

    http://lab.llvm.org:8011/builders/clang-s390x-linux/builds/27650/steps/ninja%20check%201/logs/stdio
    http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/31759
    http://lab.llvm.org:8011/builders/clang-s390x-linux-lnt/builds/15095
    http://lab.llvm.org:8011/builders/clang-ppc64be-linux-multistage/builds/21075
    http://lab.llvm.org:8011/builders/clang-ppc64be-linux-lnt/builds/31759 (detail)
    by Vitaly Buka
  5. NFC: clang-format rL374420 and adjust comment wording

    The commit of rL374420 had various formatting issues, including lines
    that exceed 80 columns. This patch applies `git clang-format` on the
    changes from commit 13bd3ef40d8b1586f26a022e01b21e56c91e05bd.

    It further adjusts a comment to clarify the domain of inputs upon which
    a newly added function is meant to operate. The adjustment to the
    comment was suggested in a post-commit comment on D68721 and discussed
    off-list with @sfertile. (detail)
    by hubert.reinterpretcast
  6. recommit: [LoopVectorize][PowerPC] Estimate int and float register pressure separately in loop-vectorize

    In loop-vectorize, interleave count and vector factor depend on target register number. Currently, it does not
    estimate different register pressure for different register class separately(especially for scalar type,
    float type should not be on the same position with int type), so it's not accurate. Specifically,
    it causes too many times interleaving/unrolling, result in too many register spills in loop body and hurting performance.

    So we need classify the register classes in IR level, and importantly these are abstract register classes,
    and are not the target register class of backend provided in td file. It's used to establish the mapping between
    the types of IR values and the number of simultaneous live ranges to which we'd like to limit for some set of those types.

    For example, POWER target, register num is special when VSX is enabled. When VSX is enabled, the number of int scalar register is 32(GPR),
    float is 64(VSR), but for int and float vector register both are 64(VSR). So there should be 2 kinds of register class when vsx is enabled,
    and 3 kinds of register class when VSX is NOT enabled.

    It runs on POWER target, it makes big(+~30%) performance improvement in one specific bmk(503.bwaves_r) of spec2017 and no other obvious degressions.

    Differential revision: https://reviews.llvm.org/D67148 (detail)
    by wuzish
  7. [clang][IFS] Updating tests to pass on -fvisibility=hidden builds (NFCi).

    Special thanks to JamesNagurne who got to the bottom of this; landing this on
    his behalf.

    Differential Revision: https://reviews.llvm.org/D68897 (detail)
    by zer0
  8. [sancov] Accommodate sancov and coverage report server for use under Windows

    Summary:
    This patch makes the following changes to SanCov and its complementary Python script in order to resolve issues pertaining to non-UNIX file paths in JSON symbolization information:
    * Convert all paths to use forward slash.
    * Update `coverage-report-server.py` to correctly handle paths to sources which contain spaces.
    * Remove Linux platform restriction for all SanCov unit tests. All SanCov tests passed when ran on my local Windows machine.

    Patch by Douglas Gliner.

    Reviewers: kcc, filcab, phosek, morehouse, vitalybuka, metzman

    Reviewed By: vitalybuka

    Subscribers: vsk, Dor1s, llvm-commits

    Tags: #sanitizers, #llvm

    Differential Revision: https://reviews.llvm.org/D51018 (detail)
    by Vitaly Buka
  9. [sancov] Use LLVM Support library JSON writer in favor of individual implementation

    Summary:
    In this diff, I've replaced the individual implementation of `JSONWriter` with `json::OStream` provided by `llvm/Support/JSON.h`.

    Important Note: The output format of the JSON is considerably different compared to the original implementation. Important differences include:
    * New line for each entry in an array (should make diffs cleaner)
    * No space between keys and colon in attributed object entries.
    * Attributes with empty strings will now print the attribute name and a quote pair rather than excluding the attribute altogether

    Examples of these differences can be seen in the changes to the sancov tests which compare the JSON output.

    Patch by Douglas Gliner.

    Reviewers: kcc, filcab, phosek, morehouse, vitalybuka, metzman

    Subscribers: mehdi_amini, dexonsmith, llvm-commits

    Tags: #sanitizers, #llvm

    Differential Revision: https://reviews.llvm.org/D68752 (detail)
    by Vitaly Buka
  10. Slightly relax restriction on exact order arguments must appear. (detail)
    by dyung

Started by timer (4 times)

This run spent:

  • 3 hr 31 min waiting;
  • 4 hr 22 min build duration;
  • 7 hr 54 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