ci: use fortran-setup for GCC, Intel LLVM and Intel Classic #834
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
gnikit
changed the title
|
This PR would supersede #833 |
awvwgk
approved these changes
Jun 9, 2024
perazz
approved these changes
Jun 10, 2024
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.
This PR replaces the manual setup of GCC, Intel LLVM and Intel Classic in our CI via the setup-fortran GA workflow.
The motivation behind this is to remove a lot of the maintenance cost + also pin the Intel compiler versions.
This PR should allow us to extend CI testing with the nvidia compilers and with more modern versions of macos on arm64.
Additional notes
I have disabled the GCC-13 + Macos-12 run since there appears to be failing due to ld linker errors stemming from the gcc cask.