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

Fix bug checksum failures #8624

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

jonathan-eq
Copy link
Contributor

@jonathan-eq jonathan-eq commented Sep 3, 2024

This commit fixes the bug where multiple realizations try to read checksum at the same time, leading it to grind to a halt.
The issue was fixed by moving the forward_model_ok_lock up a level, so that only one realization can call verify_checksum at a time. This also solved the issue where jobs would be shown as stuck in pending even though all forward model steps had completed. This was probably due to checksums all being checked and verified at the same time, which can be IO intensive.

Issue
Resolves #my_issue

Approach
Short description of the approach

(Screenshot of new behavior in GUI if applicable)

  • 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 tests pass locally (after every commit!)

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

This commit fixes the bug where multiple realizations try to read checksum
at the same time, leading it to grind to a halt.
The issue was fixed by moving the forward_model_ok_lock up a level, so
that only one realization can call `verify_checksum` at a time. This
also solved the issue where jobs would be shown as stuck in pending even though
all forward model steps had completed. This was probably due to
checksums all being checked and verified at the same time, which can be
IO intensive.
@jonathan-eq jonathan-eq added the release-notes:bug-fix Automatically categorise as bug fix in release notes label Sep 3, 2024
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.79%. Comparing base (f0fb2aa) to head (a97c15e).

Additional details and impacted files
@@              Coverage Diff              @@
##           version-10.3    #8624   +/-   ##
=============================================
  Coverage         90.79%   90.79%           
=============================================
  Files               342      342           
  Lines             20945    20945           
=============================================
  Hits              19017    19017           
  Misses             1928     1928           
Flag Coverage Δ
gui-tests 75.82% <100.00%> (ø)
integration-tests 53.98% <100.00%> (ø)
unit-tests 68.79% <100.00%> (ø)

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.

@jonathan-eq jonathan-eq merged commit 6c8da52 into equinor:version-10.3 Sep 3, 2024
35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-notes:bug-fix Automatically categorise as bug fix in release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants