-
-
Notifications
You must be signed in to change notification settings - Fork 379
[GSK-1476] introducing debug_description in test decorator #1290
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
|
@Googleton, I introduced the default message, What's left is to propagate it for every test with a custom message. |
|
Kudos, SonarCloud Quality Gate passed! |
…-1476-debug-description
…-1476-debug-description
…-1476-debug-description
Improve codestyle in websocket/utils.py
…-1476-debug-description
* performance * adjusted bold rendering * added bold to default message * statistic * metamorhpic * drift * calibration * adjusted frontend * implemented @jmsquare's feedback * fixed tests
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.
Nice work @rabah-khalek for the debug description messages!
Could you plz test to start a new instance without existing DB from main and connect an internal ML worker (so that the test function does not contain debug description), and then restart both DB and worker from this branch, to see whether the debug descriptions are updated or not.
I tested locally, it seems to be working now.
|
@Inokinoki @Googleton the backend build seems to be failing, could you please have a look? I hope it's an easy fix. |
Checked, it seems to be random network issue in the last CI. This one passes |
|
Kudos, SonarCloud Quality Gate passed! |












The idea is to describe what the debug does for every test when a user clicks on the button