Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
[Failing test] gce-cos-<branch>-ingress are timing out #75186
Which jobs are failing:
Which test(s) are failing:
Since when has it been failing:
Reason for failure:
Seems like Ingress controller kept panicing during the test (https://storage.googleapis.com/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-cos-k8sbeta-ingress/6367/artifacts/test-6724261826-master/glbc.log):
moved this from Under investigation (prioritized)
to Open PR-wait for >5 successes before "Resolved"
in 1.15 CI Signal
Mar 13, 2019
@mariantalla: Reopened this issue.
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Took a quick look, turned out job "ci-kubernetes-e2e-gce-cos-k8sbeta-ingress" doesn't skip test with the
The job config is auto-generated: https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/generated/generated.yaml
@MrHohn I think it is here
@krzyzacy We introduced that filter for Ingress-GCE tests only because we needed a way to turn off tests on specific branches.
@krzyzacy That sounds like a reasonable approach, but it means we will need to update most of the ingress tests & jobs (more on-going PRs).
Could we update that job to skip
This was referenced
Mar 18, 2019
+1 to MrHohn
We have the filter on every job config. Each individual test has the unreleased tag based on what branch it needs to be tested on. So if none of the actual tests have "Unreleased" nothing gets skipped.