Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run test suite using ifort on github runners #228

Merged
merged 33 commits into from
Feb 14, 2022

Conversation

conradtchan
Copy link
Collaborator

Type of PR:
other

Description:
Intel compilers can be installed onto github runners for free, so:

Testing:
Full test suite

Did you run the bots? no - not required

and run in parallel on github actions
no need to create logs directory
This streamlines branch protection
because labels cannot be modified without token/permissions
to add the job name into git's branch protection history
only run intel installation for system==ifort
except for benchmarks, which need consistent performance (so they won't run on forks)
"intel" was used instead of "ifort", resulting in:

 make: WARNING: value of SYSTEM = intel not recognised...
@danieljprice
Copy link
Owner

might be worth squashing the commit message on this one :)

@conradtchan conradtchan marked this pull request as ready for review February 14, 2022 22:40
@conradtchan conradtchan merged commit ba2d7e1 into danieljprice:master Feb 14, 2022
@conradtchan conradtchan deleted the intel-runners branch February 14, 2022 22:41
conradtchan added a commit that referenced this pull request Mar 1, 2022
#228 added a summary step to the build checks. This always runs, even if the build checks are skipped (scheduled builds on forks). Because no builds have passed, this returns a false fail.

This change causes the workflow to only run the summary step if it is not triggered by a schedule. This will have no effect on scheduled runs on the main repo because the summary step is not used there - it is only used as a branchy protection requirement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Actions: Use Intel OneAPI compiler to avoid needing custom runners
2 participants