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

UNSTABLE periodic / win-vs2019-cuda11.8-py3 / build #128855

Closed
huydhn opened this issue Jun 17, 2024 · 2 comments
Closed

UNSTABLE periodic / win-vs2019-cuda11.8-py3 / build #128855

huydhn opened this issue Jun 17, 2024 · 2 comments
Labels
module: ci Related to continuous integration unstable

Comments

@huydhn
Copy link
Contributor

huydhn commented Jun 17, 2024 •
edited by pytorch-bot bot
Loading

Same as #103733 and #103732. Attempt to forward fix in #128854

cc @seemethere @malfet @pytorch/pytorch-dev-infra
@pytorch-bot pytorch-bot bot added module: ci Related to continuous integration unstable labels Jun 17, 2024
@pytorch-bot PyTorch Bot
Copy link

pytorch-bot bot commented Jun 17, 2024

Hello there! From the UNSTABLE prefix in this issue title, it looks like you are attempting to unstable a job in PyTorch CI. The information I have parsed is below:
  • Job name: periodic / win-vs2019-cuda11.8-py3 / build
  • Credential: huydhn

Within ~15 minutes, periodic / win-vs2019-cuda11.8-py3 / build and all of its dependants will be unstable in PyTorch CI. Please verify that the job name looks correct. With great power comes great responsibility.

@huydhn huydhn mentioned this issue Jun 17, 2024
Closed
@huydhn
Copy link
Contributor Author

huydhn commented Jun 18, 2024

The AMI has been reverted.

@huydhn huydhn closed this as completed Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
module: ci Related to continuous integration unstable
Projects
PyTorch OSS Dev Infra
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@huydhn