Started 6 days 19 hr ago
Took 12 min

Unstable Build clang-r362923-t57391-b57391.tar.gz (Jun 10, 2019 5:15:55 AM)

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] {
[Pipeline] checkout
Updating http://llvm.org/svn/llvm-project/zorg/trunk at revision '2019-06-10T05:15:55.726 -0700'
At revision 362929

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/llvm/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/llvm/trunk at revision 362923
 U        .
At revision 362923

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/test-suite-verify-machineinstrs-aarch64-O0-g/pseudo-checkout-cfe/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.
Checking out http://llvm.org/svn/llvm-project/cfe/trunk at revision 362923
No changes for http://llvm.org/svn/llvm-project/cfe/trunk since the previous build
 U        .
At revision 362923

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.
Checking out a fresh workspace because /Users/buildslave/jenkins/workspace/test-suite-verify-machineinstrs-aarch64-O0-g/pseudo-checkout-clang-tools-extra/trunk doesn't exist
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/clang-tools-extra/trunk at revision 362923
At revision 362923

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 362923
 U        .
At revision 362923

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/test-suite-verify-machineinstrs-aarch64-O0-g/pseudo-checkout-libcxx/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.
Cleaning local Directory trunk
Checking out http://llvm.org/svn/llvm-project/libcxx/trunk at revision 362923
 U        .
At revision 362923

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.
[Pipeline] }
[Pipeline] // dir
[Pipeline] sh
At revision 362929

WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
+ CMAKE_FLAGS+=' -C ../config/tasks/cmake/caches/target-arm64-iphoneos.cmake'
+ CMAKE_FLAGS+=' -C ../config/tasks/cmake/caches/opt-O0-g.cmake'

Build Log

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

This run spent:

  • 9.2 sec waiting;
  • 12 min build duration;
  • 12 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.