Fix walltime computation bug #9228
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Because we logged finished step events before the current batch of events were processed, there were situations where the snapshot from a previous failed realization was out of date. This solves that problem. There is still a residual problem that will surface if walltime is to be computed for all steps: If a failure event for a step and its success event from the subsequent run is in the same batch of events, we can get a negative walltime computed. This problem is ignored as the walltime computation is only interesting (currently) for walltimes > 120 seconds, where this cannot happen (max time between batches is 2 seconds).
berland
added
the
release-notes:bug-fix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because we logged finished step events before the current batch of events were processed, there were situations where the snapshot from a previous failed realization was out of date.
This solves that problem. There is still a residual problem that will surface if walltime is to be computed for all steps: If a failure event for a step and its success event from the subsequent run is in the same batch of events, we can get a negative walltime computed. This problem is ignored as the walltime computation is only interesting (currently) for walltimes > 120 seconds, where this cannot happen (max time between batches is 2 seconds).
Issue
Resolves #9216
Approach
Short description of the approach
(Screenshot of new behavior in GUI if applicable)
git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')When applicable