Skip to content
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-pull-build-test-e2e-gce: broken test run #29222

Closed
k8s-github-robot opened this issue Jul 19, 2016 · 0 comments
Closed

kubernetes-pull-build-test-e2e-gce: broken test run #29222

k8s-github-robot opened this issue Jul 19, 2016 · 0 comments
Labels
area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/27911/kubernetes-pull-build-test-e2e-gce/49655/

Multiple broken tests:

Failed: [k8s.io] Downward API should provide default limits.cpu/memory from node capacity {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/downward_api.go:174
Expected error:
    <*errors.errorString | 0xc820655070>: {
        s: "gave up waiting for pod 'downward-api-d7976238-4de4-11e6-9c91-42010af00036' to be 'success or failure' after 30s",
    }
    gave up waiting for pod 'downward-api-d7976238-4de4-11e6-9c91-42010af00036' to be 'success or failure' after 30s
not to have occurred

Issues about this test specifically: #28065

Failed: [k8s.io] Port forwarding [k8s.io] With a server that expects a client request should support a client that connects, sends data, and disconnects [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/portforward.go:287
Jul 19 12:13:31.347: Pod did not start running: timed out waiting for the condition

Issues about this test specifically: #27680

Failed: [k8s.io] Networking should function for intra-pod communication [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/networking.go:225
Expected error:
    <*errors.errorString | 0xc8200c30b0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred

Issues about this test specifically: #26960 #27235

Failed: [k8s.io] Pods should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/pods.go:1135
starting pod liveness-http in namespace e2e-tests-pods-ovxfv
Expected error:
    <*errors.errorString | 0xc8200c70b0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
not to have occurred
@k8s-github-robot k8s-github-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. labels Jul 19, 2016
@fejta fejta closed this as completed Aug 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test-infra kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

2 participants