-
Notifications
You must be signed in to change notification settings - Fork 107
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
Log wall- and cputime for each finished forward model step #9103
Conversation
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.
🎉 🌮
NB: multi-cpu effects are not accounted for in this pr. |
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.
⏲️
This is meant for making statistics pr forward model step name. While testing on poly_example and local queue, there is some odd occurences of the logged message that start_time is None, this is not believed to happen often in production.
2d18dcb
to
ec2f5de
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #9103 +/- ##
==========================================
- Coverage 90.72% 90.70% -0.02%
==========================================
Files 350 350
Lines 21772 21783 +11
==========================================
+ Hits 19752 19759 +7
- Misses 2020 2024 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Issue
Resolves lack of runtime logging pr. step
Approach
:tap fast on keyboard:
git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"'
)When applicable