SkyPilot: Run AI and batch jobs on any infra (Kubernetes or 12+ clouds). Get unified execution, cost savings, and high GPU availability via a simple interface.
Before, if GCP was not enabled for smoke tests, pytest tests/test_smoke.py --generic-cloud gcp would just completely ignore the --generic-cloud option and force the test to use the first enabled cloud (currently AWS).
Now, if the cloud provided to --generic-cloud isn't enabled for smoke tests, just enable it, since that's probably what was intended.
Also, if --generic-cloud is not set, use the first actually enabled cloud, not necessarily the first default cloud. (So if you do pytest tests/test_smoke.py --gcp, it will use GCP instead of AWS as the generic cloud.)
Fixes #4327.
Tested (run the relevant ones):
[x] Code formatting: bash format.sh
[ ] Any manual or new tests for this PR (please specify below)
Before, if GCP was not enabled for smoke tests,
pytest tests/test_smoke.py --generic-cloud gcpwould just completely ignore the--generic-cloudoption and force the test to use the first enabled cloud (currently AWS).Now, if the cloud provided to
--generic-cloudisn't enabled for smoke tests, just enable it, since that's probably what was intended.Also, if
--generic-cloudis not set, use the first actually enabled cloud, not necessarily the first default cloud. (So if you dopytest tests/test_smoke.py --gcp, it will use GCP instead of AWS as the generic cloud.)Fixes #4327.
Tested (run the relevant ones):
bash format.shpytest tests/test_smoke.pypytest tests/test_smoke.py::test_fill_in_the_nameconda deactivate; bash -i tests/backward_compatibility_tests.sh