-
Notifications
You must be signed in to change notification settings - Fork 1.9k
feat(firebolt): Automatically start the engine after connection #9001
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 8 Skipped Deployments
|
KSDaemon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻 Great! Thanks for the contribution!
|
@stepansergeevitch Do unit tests work for you? I tried the |
Hey @KSDaemon |
|
@stepansergeevitch Thnx for the notes! I see... So it's kind of impossible to setup isolated unit/integration tests. Anyway it requires cloud account/connection.... |
|
@stepansergeevitch, Could you please add a console.log message at the beginning of the test suite saying that it is required to set up all those ENVs if some of the required ones are missing? This will help future contributors. UPD: NVM. |
|
@stepansergeevitch Once again — thnx for the contribution! Merging! I'll setup CI integration tests later. |
|
@stepansergeevitch Sorry for bothering you again. I created a firebolt.io account, set up everything and tried to run the tests. If the engine (drivers_test) is running, and I run tests, I get these errors: But autostart tests pass: If the engine is stopped before running tests, I get these errors: At the same time I see in firebolt.io console, that the engine was started and running. If I just comment out Can you help me with this? |
* automatically start the engine after connection * add tests * fix linter * start engine in the end of the test
… (#9040) * automatically start the engine after connection * add tests * fix linter * start engine in the end of the test Co-authored-by: Stepan Burlakov <[email protected]>
Check List
Issue Reference this PR resolves
We've received a support ticket that a customer cannot connect to a stopped engine
Description of Changes Made (if issue reference is not provided)