-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Cannot create Cloud GPU istances #901
Comments
👋 Hello @kristofkammerhofer2, thank you for raising this issue about Ultralytics HUB 🚀! This is an automated response to guide you while an Ultralytics engineer looks into this shortly. Here's how you can explore more about HUB and triage common issues:
Since you've encountered a 🐛 issue, could you help us by providing a minimum reproducible example (MRE)? This includes screenshots and a detailed step-by-step process to reproduce the issue. You can learn more about how to provide an MRE here. We appreciate your patience and will respond as soon as we can! 😊 Thank you, and stay tuned for more assistance from our team! |
@kristofkammerhofer2 thank you for the bug report! We have a known issue with GPU training and are looking into this. |
@glenn-jocher - ok, if it's a known issue, how much longer will fixing it take? Why do you accept topping up the account then? And why are you not flagging it when users are trying to do it, wasting hours of my time? |
@glenn-jocher - when is it going to be fixed? If you guys are too busy with other stuff, just refund me. |
@kristofkammerhofer2 Do you still have this issue? It should be fixed now. |
Search before asking
HUB Component
Training
Bug
After successfully setting up a cloud instance to start training the website tells me that it's initiating for about 10 minutes and then reverts back to the original state where I need to start the training again.
So the training is not happening. I've tried different GPUs so far but nothing works.
What can I do?
Environment
No response
Minimal Reproducible Example
No response
Additional
No response
The text was updated successfully, but these errors were encountered: