-
Notifications
You must be signed in to change notification settings - Fork 18
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
Problem: could not start Instances from command line #597
Conversation
Problem happened when launching with --run-fake-instance Solution: Adapt to new VMPool API that take a loop Also fix benchmarks function
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #597 +/- ##
==========================================
- Coverage 43.83% 43.80% -0.03%
==========================================
Files 55 55
Lines 4944 4947 +3
Branches 585 585
==========================================
Hits 2167 2167
- Misses 2658 2661 +3
Partials 119 119 ☔ View full report in Codecov by Sentry. |
Failed to retrieve llama text: POST 504: 504 Gateway Time-outThe server didn't respond in time. |
Is there any test to ensure that this keeps working ? |
no that I know of. We don't really test the CLI via unit test and this isa debug method |
Problem: could not start Instances from command line Problem happened when launching with --run-fake-instance Solution: Adapt to new VMPool API that take a loop Also fix benchmarks function
Problem happened when launching with --run-fake-instance
Solution: Adapt to new VMPool API that take a loop Also fix benchmarks function