Skip to content

[k8s.io] Cluster level logging using GCL should check that logs from containers are ingested in GCL {Kubernetes e2e suite} #34623

@k8s-github-robot

Description

@k8s-github-robot

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

Failed: [k8s.io] Cluster level logging using GCL should check that logs from containers are ingested in GCL {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/cluster_logging_gcl.go:67
Some log lines are still missing
Expected
    <int>: 100
to equal
    <int>: 0
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/cluster_logging_gcl.go:66

Happened on a presubmit run in #29378.

Metadata

Metadata

Assignees

Labels

kind/flakeCategorizes issue or PR as related to a flaky test.priority/backlogHigher priority than priority/awaiting-more-evidence.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions