update cheyenne compilers#268
Merged
Merged
Conversation
Contributor
Author
|
Partly Addresses CICE 329 |
16 tasks
eclare108213
approved these changes
Aug 7, 2019
lettie-roach
pushed a commit
to lettie-roach/Icepack
that referenced
this pull request
Oct 18, 2022
This file contains hidden or 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
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.
PR checklist
Update the cheyenne compiler/modules
apcraig
https://github.com/CICE-Consortium/Test-Results/wiki/782dc47be7.cheyenne.intel.190807.151906
For the record, I tested intel/17.0.1, intel/18.0.5, and intel/19.0.2. We were using the intel/17 version before. This updates to the intel/19 version. The intel/18 version produced several test failures on exact restart. At this point, I think we can assume that's a compiler bug and given intel/19 is available, we can probably ignore it. The problem comes in when someone only has intel/18 and it might produce problems for them. Should we be debugging and working around compiler problems?