Define the get_instance_status and get_job_status() methods of the BenchmarkLauncher#583
Define the get_instance_status and get_job_status() methods of the BenchmarkLauncher#583R-Palazzo wants to merge 12 commits intofeature/benchmark_launcherfrom
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## feature/benchmark_launcher #583 +/- ##
==============================================================
+ Coverage 84.58% 84.98% +0.39%
==============================================================
Files 40 40
Lines 3418 3529 +111
==============================================================
+ Hits 2891 2999 +108
- Misses 527 530 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| - Instance Name: The instance name tracked by the launcher. | ||
| - Status: The status of the instance. | ||
| """ | ||
| self._validate_compute_service() |
There was a problem hiding this comment.
don't we just need to do this once in init?
There was a problem hiding this comment.
Good point. Since we don’t expose any method to update the config after init, validating it once there should be enough. Updated in c33a1e5
| """ | ||
| raise NotImplementedError | ||
| self._validate_compute_service() | ||
| instances = self._validate_instance_names(instance_names) |
There was a problem hiding this comment.
what's the scenario where invalid instance names are being provided?
There was a problem hiding this comment.
We raise an error for invalid instance names currently:
Resolve #570
CU-86b8tmh3y
If you’d like to test the feature end to end, here’s a code snippet you can use. You only need to update the credentials and the
output_destinationso it doesn’t point to the internal benchmark destination.To use SDV Enterprise synthesizers, you’ll need to have sdv-enterprise installed in the local environment where you run the code.