Console Output

Started by upstream project "lldb-cmake" build number 4535
originally caused by:
 Started by an SCM change
Obtained zorg/jenkins/jobs/jobs/lldb-cmake-sanitized from git https://github.com/llvm/llvm-zorg.git
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor on ‘green-dragon-23’
Running on green-dragon-23 in /Users/buildslave/jenkins/workspace/lldb-cmake-sanitized
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
No credentials specified
Fetching changes from the remote Git repository
[Pipeline] }
[Pipeline] // stage
 > git rev-parse --is-inside-work-tree # timeout=10
 > git config remote.origin.url https://github.com/llvm/llvm-zorg.git # timeout=10
Fetching upstream changes from https://github.com/llvm/llvm-zorg.git
 > git --version # timeout=10
 > git fetch --tags --progress -- https://github.com/llvm/llvm-zorg.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4ec74127d5f944430d247a1b8f974fcb2f62ccc1
 > git rev-list --no-walk 4ec74127d5f944430d247a1b8f974fcb2f62ccc1 # timeout=10
Resuming build at Mon Dec 09 08:16:03 PST 2019 after Jenkins restart
Ready to run at Tue Dec 10 09:33:18 PST 2019
Resuming build at Tue Dec 10 09:33:18 PST 2019 after Jenkins restart
Ready to run at Wed Dec 11 10:42:28 PST 2019
Resuming build at Wed Dec 11 10:42:28 PST 2019 after Jenkins restart
Aborted by Vedant Kumar
Click here to forcibly terminate running steps
Aborted by Vedant Kumar
Click here to forcibly terminate running steps
Aborted by Vedant Kumar
Click here to forcibly terminate running steps
Ready to run at Sun Dec 15 10:42:01 PST 2019
Resuming build at Sun Dec 15 10:42:01 PST 2019 after Jenkins restart
Aborted by Vedant Kumar
Click here to forcibly terminate running steps
Hard kill!
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
Finished: ABORTED