Zhanghao Wu
Zhanghao Wu
The `setup-{ip}.log` should appear in the `~/sky_logs/timestamp/...`. https://github.com/skypilot-org/skypilot/blob/f49ed5aed4d180c18d7feddcb2733c61d9170441/sky/backends/cloud_vm_ray_backend.py#L1982-L1986 Just tested with the following yaml, and the `setup-ip.log` correctly shows up. ``` setup: | pip install jupyterlab run: | nohup jupyter-lab...
The logs should be on your local machine, not on the remote VM.
We now have a `--detach-setup` option now. The problem should be fixed. : )
This happens much more often recently. Do we have any idea @suquark ? :)
It seems the problem happens when the test tries to `sky start` the cluster is just stopped with `sky stop`.
This has not been observed for a while. Closed for now.
Thanks for the quick fix @suquark! Did you tried `tests/run_smoke_tests.sh test_azure_start_stop`? The error seems happening to me pretty often with that test.
> I run test_azure_start_stop & test_cancel_azure at the same time and cannot reproduce the error. Also do you mean you can trigger the error with just a single test instance...
I just tried this fix, and seems the problem still exists. It seems the problem happens when the test try to `sky start` the cluster that was just stopped with...
This issue has not been observed recently. Closing this for now. Please feel free to re-open it if it occurs again.