Use Fortran setup in workflows to access multiple compilers. #164
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
jatkinson1000
force-pushed
the
intel-workflow
branch
from
c036285
to
8bdf384
Compare
jatkinson1000
force-pushed
the
intel-workflow
branch
14 times, most recently
from
b9b90e4
to
226b09a
Compare
…ccess intel compilers.
jatkinson1000
force-pushed
the
intel-workflow
branch
from
226b09a
to
285b9ef
Compare
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.
Update test-suite workflow to use the fortran-lang github action to access intel compilers.
May close #140
At the moment we can build successfully with gcc and intel-classic compilers on ubuntu.
gcc is all good, but intel is failing on the CMakeTest asserts which #142 should resolve.
We need to decide what combinations of OS, toolchain, and standard to run the tests over - enough for sensible coverage, but not an excessive number of jobs.