Started 1 mo 2 days ago
Took 1 hr 16 min

Unstable Build clang-r361600-t56815-b56815.tar.gz (May 24, 2019 12:16:46 AM)

Issues

Found 1 issues:
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
[Pipeline] {
[Pipeline] checkout
Updating http://llvm.org/svn/llvm-project/zorg/trunk at revision '2019-05-24T00:16:46.913 -0700'
At revision 361601

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
[Pipeline] }
[Pipeline] // dir

Build Log

Revision: 358206
Changes
  1. [Power9] Add a specific heuristic to schedule the addi before the load
    When we are scheduling the load and addi, if all other heuristic didn't take effect,
    we will try to schedule the addi before the load, to hide the latency, and avoid the
    true dependency added by RA. And this only take effects for Power9.

    Differential Revision: https://reviews.llvm.org/D61930 (detail)
    by qshanz
  2. [X86] Add test case that was supposed to go with r360102.

    Found in my working area. Guess I forgot 'git add' before committing. (detail)
    by ctopper
Revision: 358206
Changes
  1. Do not resolve directory junctions for `-fdiagnostics-absolute-paths` on Windows.

    If the source file path contains directory junctions, and we resolve them when
    printing diagnostic messages, these paths look independent for an IDE.
    For example, both Visual Studio and Visual Studio Code open separate editors
    for such paths, which is not only inconvenient but might even result in losing
    changes made in one of them.

    Differential Revision: https://reviews.llvm.org/D59415 (detail)
    by ikudrin

Started by upstream project relay-test-suite-verify-machineinstrs build number 5213
originally caused by:

This run spent:

  • 1 hr 8 min waiting;
  • 1 hr 16 min build duration;
  • 1 hr 16 min total from scheduled to completion.

Identified problems

No identified problem

No problems were identified. If you know why this problem occurred, please add a suitable Cause for it.