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

[Failing Test] [sig-scheduling] SchedulerPriorities [Serial] Pod should be preferably scheduled to nodes pod can tolerate #81316

Closed
soggiest opened this issue Aug 12, 2019 · 6 comments

Comments

@soggiest
Copy link
Contributor

commented Aug 12, 2019

Which jobs are failing:
ci-kubernetes-e2e-gci-gce-serial

Which test(s) are failing:
[sig-scheduling] SchedulerPriorities [Serial] Pod should be preferably scheduled to nodes pod can tolerate

Since when has it been failing:
2019-08-10

Testgrid link:
https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-serial

Reason for failure:

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/priorities.go:220
Expected
    <string>: bootstrap-e2e-minion-group-rpd8
to equal
    <string>: bootstrap-e2e-minion-group-qvr9
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:1359

Anything else we need to know:

/milestone v1.16
/priority critical-urgent
/kind failing-test
/sig scheduling
/cc @kubernetes/sig-scheduling-misc
/cc @Verolop @jimangel @soggiest @alenkacz

@Huang-Wei

This comment has been minimized.

Copy link
Member

commented Aug 12, 2019

The code which caused the failure has been reverted by #81295.

/cc @ravisantoshgudimetla

@soggiest soggiest added this to Observing (observe test failure/flake before marking as resolved) in 1.16 CI Signal Aug 12, 2019

@jimangel

This comment has been minimized.

Copy link
Member

commented Aug 16, 2019

@Huang-Wei it still seems to be failing on test / timeout with:

error during ./hack/ginkgo-e2e.sh --ginkgo.focus=\[Serial\]|\[Disruptive\] --ginkgo.skip=\[Flaky\]|\[Feature:.+\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true (interrupted): exit status 1
 
#and

kubetest --timeout triggered

https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-serial

@Huang-Wei

This comment has been minimized.

Copy link
Member

commented Aug 16, 2019

@jimangel the testgrid is green since the PR reverting:

image

@jimangel

This comment has been minimized.

Copy link
Member

commented Aug 16, 2019

Thanks @Huang-Wei, sorry to mix up the tests.

We'll keep our eye on it for a little longer before closing and I'll make sure we have issues for the other failures.

@jimangel

This comment has been minimized.

Copy link
Member

commented Aug 16, 2019

/close

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

commented Aug 16, 2019

@jimangel: Closing this issue.

In response to this:

/close

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.

@jimangel jimangel moved this from Observing (observe test failure/flake before marking as resolved) to Resolved (week Aug 12) in 1.16 CI Signal Aug 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
You can’t perform that action at this time.