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

[job failure] gke-device-plugin-gpu-p100 #56090

Closed
spiffxp opened this issue Nov 20, 2017 · 6 comments
Closed

[job failure] gke-device-plugin-gpu-p100 #56090

spiffxp opened this issue Nov 20, 2017 · 6 comments
Assignees
Labels
area/provider/gcp Issues or PRs related to gcp provider kind/bug Categorizes issue or PR as related to a bug. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. milestone/needs-attention priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Milestone

Comments

@spiffxp
Copy link
Member

spiffxp commented Nov 20, 2017

/priority critical-urgent
/priority failing-test
/area platform/gke
/kind bug
/status approved-for-milestone
@kubernetes/sig-gcp-test-failures

This job has been failing since 2017-11-18. It's on the sig-release-master-blocking dashboard,
and prevents us from cutting [v1.9.0-beta.1] (kubernetes/sig-release#34). Is there work ongoing to bring this job back to green?

https://k8s-testgrid.appspot.com/sig-release-master-blocking#gke-device-plugin-gpu-p100

@spiffxp spiffxp added this to the v1.9 milestone Nov 20, 2017
@k8s-ci-robot k8s-ci-robot added sig/gcp priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. area/provider/gcp Issues or PRs related to gcp provider kind/bug Categorizes issue or PR as related to a bug. labels Nov 20, 2017
@abgworrall
Copy link
Contributor

/assign @mindprince

Rohit, is this related to the other failing suite ?

@rohitagarwal003
Copy link
Member

Yes. This is the same issue as #56078 and should be fixed soon.

@k8s-github-robot
Copy link

[MILESTONENOTIFIER] Milestone Issue Needs Attention

@mindprince @spiffxp @kubernetes/sig-gcp-misc

Action required: During code slush, issues in the milestone should be in progress.
If this issue is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight issues.

Note: This issue is marked as priority/critical-urgent, and must be updated every 3 days during code slush.

Example update:

ACK.  In progress
ETA: DD/MM/YYYY
Risks: Complicated fix required
Issue Labels
  • sig/gcp: Issue will be escalated to these SIGs if needed.
  • priority/critical-urgent: Never automatically move issue out of a release milestone; continually escalate to contributor and SIG through all available channels.
  • kind/bug: Fixes a bug discovered during the current release.
Help

@spiffxp
Copy link
Member Author

spiffxp commented Nov 22, 2017

FYI this is still failing, it may be that I haven't seen a run yet since you've rolled out the GKE-related change

@rohitagarwal003
Copy link
Member

Yes, it's an expensive test and runs only every 12 hours. It should pass in the next run.

@rohitagarwal003
Copy link
Member

/close
Latest run passed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/gcp Issues or PRs related to gcp provider kind/bug Categorizes issue or PR as related to a bug. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. milestone/needs-attention priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

5 participants