Started 27 days ago
Took 1 hr 4 min on green-dragon-17

Failed Build rL:372686 - C:372689 - #755 (Sep 23, 2019 11:53:13 PM)

Revisions
  • http://llvm.org/svn/llvm-project/llvm/trunk : 372686
  • http://llvm.org/svn/llvm-project/cfe/trunk : 372689
  • http://llvm.org/svn/llvm-project/compiler-rt/trunk : 372684
  • http://llvm.org/svn/llvm-project/debuginfo-tests/trunk : 364589
  • http://llvm.org/svn/llvm-project/zorg/trunk : 372433
  • http://llvm.org/svn/llvm-project/libcxx/trunk : 372632
  • http://llvm.org/svn/llvm-project/clang-tools-extra/trunk : 372627
Changes
  1. [clang-format] NFC clang-format the clang-format unit tests

    Summary:
    It is annoying that the clang-format tests aren't themselves clang-formatted, if you use a format on save option in VS or vim this file gets massively changed then you have to `git difftool` all the other changes back out, which is risky.

    I know people don't like mass clang-format changes but sometimes it becomes unmanageable to not. There are no other changes here other than just the reformat.

    clang-format tests all pass.

    ```
    [==========] 691 tests from 21 test cases ran. (55990 ms total)
    [  PASSED  ] 691 tests.
    ```

    Reviewers: klimek, owenpan, timwoj

    Reviewed By: owenpan

    Subscribers: cfe-commits

    Tags: #clang-tools-extra, #clang

    Differential Revision: https://reviews.llvm.org/D67888 (detail/ViewSVN)
    by paulhoad

Started by an SCM change

This run spent:

  • 16 min waiting;
  • 1 hr 4 min build duration;
  • 1 hr 20 min total from scheduled to completion.
LLVM/Clang Warnings: 3 warnings.

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

Assertion failure

This build failed because of an assertion failure. Below is a list of all errors in the build log:
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

Missing test results

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