-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
ci-kubernetes-e2e-gci-gce-alpha-features is failing #53425
Labels
kind/bug
Categorizes issue or PR as related to a bug.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
Comments
k8s-ci-robot
added
kind/bug
Categorizes issue or PR as related to a bug.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
labels
Oct 4, 2017
/assign @k82cn |
@msau42 , do you know how to trigger this test in CI, e.g. |
I don't think there's a way to launch a ci job from here. |
sure, let me add some instrument code and trigger test by |
k8s-github-robot
pushed a commit
that referenced
this issue
Oct 6, 2017
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Refresh scheduler equivalence cache when node taints changed. **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #53425 **Release note**: ```release-note None ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
sig/scheduling
Categorizes an issue or PR as relevant to SIG Scheduling.
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
alpha suite has been failing in the BeforeSuite since 9/22
logs
testgrid
Did we recently enable some alpha taints feature? @kubernetes/sig-scheduling-bugs
The text was updated successfully, but these errors were encountered: