Fix <= .to3 migrations causing .to7 gendata migration failure #9048
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.
.to3
migrations are currently dumping responses.json based on theResponseConfig
, so then it is already migrated. Code in.to7
assumes it is not migrated. This was also not being caught by the storage migration test as it checked only for summary data.Checking for it in the test makes it fail: https://github.com/equinor/ert/actions/runs/11514769298/job/32054192381