SuccessConsole Output

Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
Running as SYSTEM
Building remotely on green-dragon-05 (Zorg 10.11) in workspace /Users/buildslave/jenkins/libcxx_libcxxabi_trunk_testing
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url http://labmaster3.local/git/llvm-project.git # timeout=10
Fetching upstream changes from http://labmaster3.local/git/llvm-project.git
 > git --version # timeout=10
 > git fetch --tags --progress http://labmaster3.local/git/llvm-project.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/refs/heads/master^{commit} # timeout=10
Checking out Revision 85f7294e5af0cb7ea8e2d0469b96d0369627c48c (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 85f7294e5af0cb7ea8e2d0469b96d0369627c48c
Commit message: "[analyzer] CastValueChecker: Correctly model results of based-to-derived casts."
 > git rev-list --no-walk 347c7d682e5a88bcc94a2cfa4aaaf48536473418 # timeout=10
No emails were triggered.
New run name is '#266 std= arch= exceptions='
Triggering libc++ and libc++abi trunk » 64,ON,c++17
Configuration libc++ and libc++abi trunk » 64,ON,c++17 is still in the queue: ‘Jenkins’ is reserved for jobs with matching label expression
‘green-dragon-05’ is reserved for jobs with matching label expression
‘green-dragon-07’ is reserved for jobs with matching label expression
‘green-dragon-10’ is reserved for jobs with matching label expression
‘green-dragon-11’ is reserved for jobs with matching label expression
‘green-dragon-13’ is reserved for jobs with matching label expression
‘green-dragon-14’ is reserved for jobs with matching label expression
‘green-dragon-21’ is reserved for jobs with matching label expression
‘green-dragon-24’ is reserved for jobs with matching label expression
‘labmaster2’ is reserved for jobs with matching label expression
Configuration libc++ and libc++abi trunk » 64,ON,c++17 is still in the queue: ‘Jenkins’ is reserved for jobs with matching label expression
‘green-dragon-05’ is reserved for jobs with matching label expression
‘green-dragon-07’ is reserved for jobs with matching label expression
‘green-dragon-10’ is reserved for jobs with matching label expression
‘green-dragon-11’ is reserved for jobs with matching label expression
‘green-dragon-12’ is reserved for jobs with matching label expression
‘green-dragon-13’ is reserved for jobs with matching label expression
‘green-dragon-14’ is reserved for jobs with matching label expression
‘green-dragon-21’ is reserved for jobs with matching label expression
‘green-dragon-24’ is reserved for jobs with matching label expression
‘labmaster2’ is reserved for jobs with matching label expression
Configuration libc++ and libc++abi trunk » 64,ON,c++17 is still in the queue: ‘Jenkins’ is reserved for jobs with matching label expression
‘green-dragon-05’ is reserved for jobs with matching label expression
‘green-dragon-07’ is reserved for jobs with matching label expression
‘green-dragon-10’ is reserved for jobs with matching label expression
‘green-dragon-11’ is reserved for jobs with matching label expression
‘green-dragon-13’ is reserved for jobs with matching label expression
‘green-dragon-14’ is reserved for jobs with matching label expression
‘green-dragon-21’ is reserved for jobs with matching label expression
‘green-dragon-24’ is reserved for jobs with matching label expression
‘labmaster2’ is reserved for jobs with matching label expression
Configuration libc++ and libc++abi trunk » 64,ON,c++17 is still in the queue: ‘Jenkins’ is reserved for jobs with matching label expression
‘green-dragon-05’ is reserved for jobs with matching label expression
‘green-dragon-07’ is reserved for jobs with matching label expression
‘green-dragon-10’ is reserved for jobs with matching label expression
‘green-dragon-11’ is reserved for jobs with matching label expression
‘green-dragon-13’ is reserved for jobs with matching label expression
‘green-dragon-14’ is reserved for jobs with matching label expression
‘green-dragon-21’ is reserved for jobs with matching label expression
‘labmaster2’ is reserved for jobs with matching label expression
Configuration libc++ and libc++abi trunk » 64,ON,c++17 is still in the queue: ‘Jenkins’ is reserved for jobs with matching label expression
‘green-dragon-05’ is reserved for jobs with matching label expression
‘green-dragon-07’ is reserved for jobs with matching label expression
‘green-dragon-10’ is reserved for jobs with matching label expression
‘green-dragon-11’ is reserved for jobs with matching label expression
‘green-dragon-13’ is reserved for jobs with matching label expression
‘green-dragon-14’ is reserved for jobs with matching label expression
‘green-dragon-21’ is reserved for jobs with matching label expression
‘green-dragon-24’ is reserved for jobs with matching label expression
‘labmaster2’ is reserved for jobs with matching label expression
libc++ and libc++abi trunk » 64,ON,c++17 completed with result SUCCESS
Triggering libc++ and libc++abi trunk » 32,OFF,c++14
Triggering libc++ and libc++abi trunk » 32,ON,c++17
Triggering libc++ and libc++abi trunk » 32,ON,c++2a
Triggering libc++ and libc++abi trunk » 64,ON,c++03
Triggering libc++ and libc++abi trunk » 32,OFF,c++98
Triggering libc++ and libc++abi trunk » 32,OFF,c++2a
Triggering libc++ and libc++abi trunk » 32,ON,c++98
Triggering libc++ and libc++abi trunk » 64,ON,c++14
Triggering libc++ and libc++abi trunk » 64,OFF,c++98
Triggering libc++ and libc++abi trunk » 32,ON,c++14
Triggering libc++ and libc++abi trunk » 64,ON,c++11
Triggering libc++ and libc++abi trunk » 64,OFF,c++03
Triggering libc++ and libc++abi trunk » 64,OFF,c++2a
Triggering libc++ and libc++abi trunk » 32,OFF,c++03
Triggering libc++ and libc++abi trunk » 64,OFF,c++14
Triggering libc++ and libc++abi trunk » 32,OFF,c++11
Triggering libc++ and libc++abi trunk » 32,ON,c++11
Triggering libc++ and libc++abi trunk » 64,OFF,c++17
Triggering libc++ and libc++abi trunk » 64,ON,c++2a
Triggering libc++ and libc++abi trunk » 32,ON,c++03
Triggering libc++ and libc++abi trunk » 32,OFF,c++17
Triggering libc++ and libc++abi trunk » 64,ON,c++98
Triggering libc++ and libc++abi trunk » 64,OFF,c++11
libc++ and libc++abi trunk » 32,OFF,c++14 completed with result SUCCESS
libc++ and libc++abi trunk » 32,ON,c++17 completed with result SUCCESS
libc++ and libc++abi trunk » 32,ON,c++2a completed with result SUCCESS
libc++ and libc++abi trunk » 64,ON,c++03 completed with result SUCCESS
libc++ and libc++abi trunk » 32,OFF,c++98 completed with result SUCCESS
libc++ and libc++abi trunk » 32,OFF,c++2a completed with result SUCCESS
libc++ and libc++abi trunk » 32,ON,c++98 completed with result SUCCESS
libc++ and libc++abi trunk » 64,ON,c++14 completed with result SUCCESS
libc++ and libc++abi trunk » 64,OFF,c++98 completed with result SUCCESS
libc++ and libc++abi trunk » 32,ON,c++14 completed with result SUCCESS
libc++ and libc++abi trunk » 64,ON,c++11 completed with result SUCCESS
libc++ and libc++abi trunk » 64,OFF,c++03 completed with result SUCCESS
libc++ and libc++abi trunk » 64,OFF,c++2a completed with result SUCCESS
libc++ and libc++abi trunk » 32,OFF,c++03 completed with result SUCCESS
libc++ and libc++abi trunk » 64,OFF,c++14 completed with result SUCCESS
libc++ and libc++abi trunk » 32,OFF,c++11 completed with result SUCCESS
libc++ and libc++abi trunk » 32,ON,c++11 completed with result SUCCESS
libc++ and libc++abi trunk » 64,OFF,c++17 completed with result SUCCESS
libc++ and libc++abi trunk » 64,ON,c++2a completed with result SUCCESS
libc++ and libc++abi trunk » 32,ON,c++03 completed with result SUCCESS
libc++ and libc++abi trunk » 32,OFF,c++17 completed with result SUCCESS
libc++ and libc++abi trunk » 64,ON,c++98 completed with result SUCCESS
libc++ and libc++abi trunk » 64,OFF,c++11 completed with result SUCCESS
No emails were triggered.
New run name is '#266 std= arch= exceptions='
Finished: SUCCESS