Started 2 mo 13 days ago
Took 4 min 57 sec

Unstable Build clang-r362976-t57413-b57413.tar.gz (Jun 10, 2019 2:02:22 PM)

Issues

Found 7 issues:
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
[Pipeline] // dir
[Pipeline] dir
Running in /Users/buildslave/jenkins/workspace/lnt-ctmark-aarch64-O0-g/pseudo-checkout-llvm
[Pipeline] {
[Pipeline] checkout
WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
[Pipeline] }
[Pipeline] // dir
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/llvm/trunk at revision 362976
 U        .
At revision 362976

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
No changes for http://llvm.org/svn/llvm-project/cfe/trunk since the previous build
[Pipeline] }
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/cfe/trunk at revision 362976
 U        .
At revision 362976

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Checking out a fresh workspace because /Users/buildslave/jenkins/workspace/lnt-ctmark-aarch64-O0-g/pseudo-checkout-clang-tools-extra/trunk doesn't exist
Cleaning local Directory trunk
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Running in /Users/buildslave/jenkins/workspace/lnt-ctmark-aarch64-O0-g/pseudo-checkout-compiler-rt
[Pipeline] {
[Pipeline] checkout
At revision 362976

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
No changes for http://llvm.org/svn/llvm-project/compiler-rt/trunk since the previous build
[Pipeline] }
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/compiler-rt/trunk at revision 362976
 U        .
At revision 362976

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
No changes for http://llvm.org/svn/llvm-project/libcxx/trunk since the previous build
[Pipeline] }
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/libcxx/trunk at revision 362976
 U        .
At revision 362976

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
No changes for http://llvm.org/svn/llvm-project/lnt/trunk since the previous build
[Pipeline] }
Warning: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
[Pipeline] {
[Pipeline] svn
Updating http://llvm.org/svn/llvm-project/lnt/trunk at revision '2019-06-10T14:02:22.256 -0700'
At revision 362982

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
Updating http://llvm.org/svn/llvm-project/test-suite/trunk at revision '2019-06-10T14:02:22.256 -0700'
No changes for http://llvm.org/svn/llvm-project/test-suite/trunk since the previous build

Build Log

Revision: 362564
Changes
  1. [Tests] Add tests for D62939 (miscompiles around dead pointer IVs)

    Flesh out a collection of tests for switching to a dead IV within LFTR, both for the current miscompile, and for some cases which we should be able to handle via simple reasoning. (detail)
    by reames

Started by upstream project relay-lnt-ctmark build number 8592
originally caused by:

This run spent:

  • 7.7 sec waiting;
  • 4 min 57 sec build duration;
  • 5 min 5 sec 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.