Skip to content
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

Merged
merged 2 commits into from
Oct 31, 2024

Conversation

berland
Copy link
Contributor

@berland berland commented Oct 30, 2024

Issue
Resolves lack of runtime logging pr. step

Approach
:tap fast on keyboard:

  • PR title captures the intent of the changes, and is fitting for release notes.
  • Added appropriate release note label
  • Commit history is consistent and clean, in line with the contribution guidelines.
  • Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

When applicable

  • When there are user facing changes: Updated documentation
  • New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
  • Large PR: Prepare changes in small commits for more convenient review
  • Bug fix: Add regression test for the bug
  • Bug fix: Create Backport PR to latest release

Copy link
Contributor

@eivindjahren eivindjahren left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉 🌮

@berland
Copy link
Contributor Author

berland commented Oct 31, 2024

NB: multi-cpu effects are not accounted for in this pr.

Copy link
Collaborator

@sondreso sondreso left a 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.
@berland berland added the release-notes:maintenance Automatically categorise as maintenance change in release notes label Oct 31, 2024
@berland berland changed the title Log step runtime Log wall- and cputime for each finished forward model step Oct 31, 2024
@berland berland self-assigned this Oct 31, 2024
@berland berland enabled auto-merge (rebase) October 31, 2024 08:17
@berland berland merged commit c4e1365 into equinor:main Oct 31, 2024
56 checks passed
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.70%. Comparing base (f934735) to head (ec2f5de).
Report is 4 commits behind head on main.

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     
Flag Coverage Δ
cli-tests 39.02% <81.81%> (-0.03%) ⬇️
gui-tests 71.68% <81.81%> (-0.02%) ⬇️
performance-tests 49.24% <90.90%> (+<0.01%) ⬆️
unit-tests 79.55% <100.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes:maintenance Automatically categorise as maintenance change in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants