-
Notifications
You must be signed in to change notification settings - Fork 168
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
test: use ACTS logging for Navigator tests #3312
Conversation
📊: Physics performance monitoring for a9ce03cphysmon summary
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3312 +/- ##
==========================================
+ Coverage 47.24% 47.31% +0.07%
==========================================
Files 508 512 +4
Lines 30041 30441 +400
Branches 14586 14795 +209
==========================================
+ Hits 14192 14404 +212
- Misses 5375 5404 +29
- Partials 10474 10633 +159 ☔ View full report in Codecov by Sentry. |
I think it is not strictly necessary to use logger in our tests over |
It's probably not necessary, since we don't evoke our test suite with different logging levels and therefore need to recompile anyhow when we want to have more or less output. However, I changed it, after going through the test and I understood, that the variables |
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.
👍
Quality Gate passedIssues Measures |
blocked by:
Navigator
consistency checks to integration tests #3315