-
Notifications
You must be signed in to change notification settings - Fork 247
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
feat_: status-backend health endpoint #6201
Conversation
Jenkins BuildsClick to see older builds (26)
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6201 +/- ##
========================================
Coverage 61.41% 61.42%
========================================
Files 833 834 +1
Lines 109925 109934 +9
========================================
+ Hits 67511 67526 +15
- Misses 34518 34522 +4
+ Partials 7896 7886 -10
Flags with carried forward coverage won't be shown. Click here to find out more.
|
663c482
to
a97309c
Compare
@antdanchenko please take another look, I added |
backend_client.verify_json_schema( | ||
backend_client.wait_for_login(), "signal_node_login") |
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.
It's better to check login first, because it properly processes results of restore_account_and_login
in case of an error. While other signals are just never sent in case of an error.
c4a7191
to
bc8398d
Compare
bc8398d
to
af757a2
Compare
status-backend
At first I brought back docker healthcheck feature, but it didn't make sense. Even having it running in background, we wouldn't get notified and stop the tests. And it wouldn't work when running
status-backend
locally not in docker.At the same time all tests have timeout for all requests.