Skip to content

Add Intel compiler build to CI#36

Draft
junghans wants to merge 2 commits into
kokkos:developfrom
junghans:intel
Draft

Add Intel compiler build to CI#36
junghans wants to merge 2 commits into
kokkos:developfrom
junghans:intel

Conversation

@junghans
Copy link
Copy Markdown
Contributor

@junghans junghans commented Oct 30, 2020

Something is still wrong with ifort and I am a bit unhappy with the runtime.

@certik
Copy link
Copy Markdown

certik commented Nov 9, 2020

If you ever figure out how to use Intel compilers at a GitHub CI, faster than with 1h installation time, that would be really awesome. I would use it in a lot of projects.

@junghans
Copy link
Copy Markdown
Contributor Author

junghans commented Nov 9, 2020

If you ever figure out how to use Intel compilers at a GitHub CI, faster than with 1h installation time, that would be really awesome. I would use it in a lot of projects.

@certik you could make a container that contains everything, but the trial license, e.g. https://github.com/votca/buildenv/blob/master/fedora

@womeld
Copy link
Copy Markdown
Contributor

womeld commented Nov 9, 2020

I apologize for not foreseeing this, but I had forgot to set the default branch of the project to 'develop'. I've since done so, and hopefully that does not cause any problems here. (The spackage only has targets for the release that supports spack, and develop.)

@junghans junghans changed the base branch from master to develop November 9, 2020 23:40
@junghans
Copy link
Copy Markdown
Contributor Author

junghans commented Nov 9, 2020

@certik PS: I could make the CI here based on ghcr.io/votca/buildenv/fedora:intel and be done, but relying on another projects container just seems wrong.

@certik
Copy link
Copy Markdown

certik commented Nov 9, 2020

At GitLab I reuse containers all the time, but I always make a project specific ci-images repository, such as:

https://gitlab.com/lfortran/ci-images
https://gitlab.com/truchas/ci-images
https://gitlab.com/ftpum/ci-images
...

Cannot you just copy the container and maintain it here for this project?

@junghans
Copy link
Copy Markdown
Contributor Author

junghans commented Nov 9, 2020

Ultimately I will do that, currently I still need to figure out how to solve the ifort issue.

echo "/opt/intel/bin" >> $GITHUB_PATH
- name: Get trial license
run: |
mkdir ~/Licenses
Copy link
Copy Markdown
Contributor Author

@junghans junghans Nov 10, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@certik Does the line below answer your question?

Comment on lines +28 to +36
curl -O http://registrationcenter-download.intel.com/akdlm/irc_nas/tec/16756/parallel_studio_xe_2020_update2_professional_edition.tgz
tar -xf parallel_studio_xe_*.tgz
pushd parallel_studio_xe_*/rpm
printf "[icc]\nname=icc\nbaseurl=$PWD\nenabled=1" | sudo tee -a /etc/yum.repos.d/icc.repo
popd
sudo dnf -y update
sudo dnf --nogpgcheck -y install intel-parallel-studio-xe-icc intel-parallel-studio-xe-mkl intel-parallel-studio-xe-ifort
echo "LD_LIBRARY_PATH=/opt/intel/lib/intel64:/opt/intel/mkl/lib/intel64" >> $GITHUB_ENV
echo "/opt/intel/bin" >> $GITHUB_PATH
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dalg24 this part, downloading/installing icc, takes 30 min, so if we can create a base container and store it on Github's ghcr.io that would help a lot. We could use the same container to test kokkos with icc as well.

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.

3 participants