New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kubernetes-verify-master: broken test run #31191
Comments
Looks like some intermittent networking problems:
|
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3283/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3287/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3290/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3343/ Run so broken it didn't make JUnit output! |
[FLAKE-PING] @apelisse This flaky-test issue would love to have more attention... |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3487/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3493/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3494/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3495/ Run so broken it didn't make JUnit output! |
[FLAKE-PING] @apelisse This flaky-test issue would love to have more attention. |
2 similar comments
[FLAKE-PING] @apelisse This flaky-test issue would love to have more attention. |
[FLAKE-PING] @apelisse This flaky-test issue would love to have more attention. |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3665/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3666/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3667/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3668/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3718/ Run so broken it didn't make JUnit output! |
3178: git clone failed in verify-godeps.sh |
mungedocs probably not broken by that PR, but I'm not sure of root cause yet. could be a flaky check. |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3719/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3720/ Run so broken it didn't make JUnit output! |
…om S3. This has been causing flakes: kubernetes#31191, kubernetes#31492 This includes a hash of the tarball to ensure that the correct file is downloaded, either from GCS or S3. Tested manually with: ( . hack/lib/init.sh; kube::etcd::install ) gsutil rm gs://kubernetes-jenkins/dependencies/etcd/etcd-v3.0.4-linux-amd64.tar.gz
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3721/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3722/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3723/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3724/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3725/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3726/ Run so broken it didn't make JUnit output! |
Reassign to @rmmh since he's working on etcd download caching. |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3784/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3785/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3786/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3787/ Run so broken it didn't make JUnit output! |
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3788/ Run so broken it didn't make JUnit output! |
^ These 5 are all from a pull that broke verify-munge-docs. It shouldn't recur since kubernetes/test-infra#536 was merged. |
Closing because the sub-issues have been fixed. Let's track the etcd flakes separately.
|
…om S3. This has been causing flakes: kubernetes#31191, kubernetes#31492 This includes a hash of the tarball to ensure that the correct file is downloaded, either from GCS or S3. Tested manually with: ( . hack/lib/init.sh; kube::etcd::install ) gsutil rm gs://kubernetes-jenkins/dependencies/etcd/etcd-v3.0.4-linux-amd64.tar.gz
Failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-verify-master/3178/
Run so broken it didn't make JUnit output!
The text was updated successfully, but these errors were encountered: