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.

Sign up for GitHub

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

Jump to bottom

CI: Re-enable GPU integration testing #3590

Closed
tstromberg opened this issue Jan 25, 2019 · 1 comment
Closed

CI: Re-enable GPU integration testing #3590

tstromberg opened this issue Jan 25, 2019 · 1 comment
Labels
area/gpu GPU related items area/testing lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. r/2019q2 Issue was last reviewed 2019q2 triage/unresolved Indicates an issue that can not or will not be resolved.

Comments

@tstromberg
Copy link
Contributor

Not sure where this is at. @balopat - any clue what the blockers are here?
@tstromberg tstromberg added area/testing area/gpu GPU related items labels Jan 25, 2019
@tstromberg tstromberg changed the title CI: Re-enable GPU testing CI: Re-enable GPU integration testing Jan 25, 2019
@tstromberg tstromberg added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jan 25, 2019
@tstromberg tstromberg mentioned this issue Jan 25, 2019
Closed
@tstromberg tstromberg added this to the v1.0.0-candidate milestone Jan 25, 2019
@tstromberg tstromberg removed this from the v1.0.0 milestone Mar 20, 2019
@tstromberg tstromberg added the r/2019q2 Issue was last reviewed 2019q2 label Apr 4, 2019
@tstromberg tstromberg added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Apr 16, 2019
@tstromberg tstromberg added this to the v1.1.0-candidate milestone Apr 16, 2019
@tstromberg tstromberg removed this from the v1.1.0-candidate milestone May 1, 2019
@tstromberg tstromberg added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels May 30, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 28, 2019
@tstromberg tstromberg added the triage/unresolved Indicates an issue that can not or will not be resolved. label Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/gpu GPU related items area/testing lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. r/2019q2 Issue was last reviewed 2019q2 triage/unresolved Indicates an issue that can not or will not be resolved.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tstromberg @k8s-ci-robot @fejta-bot