This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2019-10-22 06:58
Elapsed17m42s
Revision
Buildergke-prow-ssd-pool-1a225945-bfs0
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/c0caabe5-5bfb-4d8d-ba3f-66caa1262573/targets/test'}}
pod3dae5068-f499-11e9-b7ad-c2d16e8c74e9
resultstorehttps://source.cloud.google.com/results/invocations/c0caabe5-5bfb-4d8d-ba3f-66caa1262573/targets/test
infra-commit29142f33c
pod3dae5068-f499-11e9-b7ad-c2d16e8c74e9
repok8s.io/kubernetes
repo-commit3ff376923d84ecf41f3fb149390f415764e98806
repos{u'k8s.io/kubernetes': u'master', u'k8s.io/release': u'master'}

No Test Failures!


Error lines from build-log.txt

... skipping 158 lines ...
I1022 07:15:59.630] Checking write access to bucket k8s-staging-release-test: 
I1022 07:15:59.631] push-build.sh::release::gcs::check_release_bucket(): touch /tmp/push-build.sh-gcs-write.53714
I1022 07:15:59.636] 
I1022 07:15:59.636] push-build.sh::release::gcs::check_release_bucket(): /google-cloud-sdk/bin/gsutil cp /tmp/push-build.sh-gcs-write.53714 gs://k8s-staging-release-test
I1022 07:16:00.636] Copying file:///tmp/push-build.sh-gcs-write.53714 [Content-Type=application/octet-stream]...
I1022 07:16:00.789] / [0 files][    0.0 B/    0.0 B]                                                
AccessDeniedException: 403 pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com does not have storage.objects.create access to k8s-staging-release-test/push-build.sh-gcs-write.53714.
I1022 07:16:00.938] FAILED: You do not have access/write permission on k8s-staging-release-test. Unable
I1022 07:16:00.939] to continue.
I1022 07:16:00.944] FAILED
I1022 07:16:00.949] 
I1022 07:16:00.954] push-build.sh: DONE main on 3dae5068-f499-11e9-b7ad-c2d16e8c74e9 Tue Oct 22 07:16:00 UTC 2019 in 3s
W1022 07:16:00.963] Traceback (most recent call last):
W1022 07:16:00.963]   File "/workspace/./test-infra/jenkins/../scenarios/kubernetes_build.py", line 165, in <module>
W1022 07:16:00.964]     main(ARGS)
W1022 07:16:00.964]   File "/workspace/./test-infra/jenkins/../scenarios/kubernetes_build.py", line 137, in main
W1022 07:16:00.964]     check(args.push_build_script, *push_build_args)
W1022 07:16:00.964]   File "/workspace/./test-infra/jenkins/../scenarios/kubernetes_build.py", line 32, in check
W1022 07:16:00.965]     subprocess.check_call(cmd)
W1022 07:16:00.965]   File "/usr/lib/python2.7/subprocess.py", line 190, in check_call
W1022 07:16:00.965]     raise CalledProcessError(retcode, cmd)
W1022 07:16:00.965] subprocess.CalledProcessError: Command '('../release/push-build.sh', '--nomock', '--verbose', '--ci', '--release-kind=kubernetes', '--bucket=k8s-staging-release-test', '--allow-dup')' returned non-zero exit status 1
E1022 07:16:00.965] Command failed
I1022 07:16:00.966] process 511 exited with code 1 after 16.3m
E1022 07:16:00.966] FAIL: ci-kubernetes-shadow-build-fast
I1022 07:16:00.966] Call:  gcloud auth activate-service-account --key-file=/etc/service-account/service-account.json
W1022 07:16:01.510] Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
I1022 07:16:01.578] process 54175 exited with code 0 after 0.0m
I1022 07:16:01.579] Call:  gcloud config get-value account
I1022 07:16:01.921] process 54187 exited with code 0 after 0.0m
I1022 07:16:01.921] Will upload results to gs://kubernetes-jenkins/logs using pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com
... skipping 20 lines ...