kokkos-fortran-interop icon indicating copy to clipboard operation
kokkos-fortran-interop copied to clipboard

Add Intel compiler build to CI

Open junghans opened this issue 3 years ago • 6 comments

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

junghans avatar Oct 30 '20 01:10 junghans

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 avatar Nov 09 '20 23:11 certik

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

junghans avatar Nov 09 '20 23:11 junghans

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.)

womeld avatar Nov 09 '20 23:11 womeld

@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.

junghans avatar Nov 09 '20 23:11 junghans

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?

certik avatar Nov 09 '20 23:11 certik

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

junghans avatar Nov 09 '20 23:11 junghans