Closed MislavSag closed 4 years ago
Thanks for opening this issue! This is a bug on our side and we will fix this ASAP.
I think the fix right now is just to do n_jobs=None.
BTW @MislavSag is this possible to reproduce on colab?
Don't have time right now, I am going to vacation tomorrow. Maybe in 2 weeks if that's not too late.
No problem @MislavSag; enjoy your vacation and stay safe!
@richardliaw I get this error with tune.run. I have a machine with 4 cpus and 1 gpu. I initiate ray with cpu=3 and gpu=1 and from within tune.run, resources_per_trial={"cpu": 1, "gpu": 0.5}. At first, no error. 2 trails run parallel and around 20 trails get completes, however, after a while, I get this error:
"ray.tune.error.TuneError: Insufficient cluster resources to launch trial: trial requested 1 CPUs, 0.5 GPUs but the cluster has only 0 CPUs, 0 GPUs, 0.0 GiB heap, 0.0 GiB objects. Pass queue_trials=True
in ray.tune.run() or on the command line to queue trials until the cluster scales up or resources become available."
Is this because of the bug you have pointed out earlier in the thread?
@nasrin136 thanks for reaching out!
No, that sounds like another problem (actually more concerning). Could you post this issue on ray-project/ray and ping me when you do?
Thanks @richardliaw for the prompt response. Done. and here is the link: https://github.com/ray-project/ray/issues/10756
closing because stale/addressed
I have just tried
TuneSearchCV
function withsearch_optimization='bayesian'
option:I get the following output: