Debugging non-reproducibility of ACCESS-NRI 0.3.0 -> 0.4.0 #46
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.
This is a PR to debug and document where we lost reproducibility when we updated from 0.3.0 to 0.4.0. The context is that our repro tests had a bug and was effectively always reporting reproducible runs. We thus updated components from 0.3.0 to 0.4.0 under the impression that the updates were not answer-changing when in fact they are.
See COSIMA/access-om3#266
🚀 The latest prerelease
access-om3/pr46-2
at 4352908 is here: #46 (comment) 🚀