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.

Sign up for GitHub

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

Jump to bottom

Tests with ifort #54

Open
andreww opened this issue Apr 5, 2018 · 3 comments
Open

Tests with ifort #54

andreww opened this issue Apr 5, 2018 · 3 comments

Comments

@andreww
Copy link
Owner

andreww commented Apr 5, 2018

In an ideal world we would run CI tests with other compilers, and ifort would be the obvious one (as that's still well used). I should look at that.

One problem will be that new(ish) iforts add "abort:" at the end of tests which abort. We could work around this for gortran by doing BUILD_SCRIPT="FC='gfortran -fno-backtrace' ./configure && ... (see d2ad441). The ifort version, BUILD_SCRIPT="FC='ifort -notraceback' ./configure && leaves the "abort:" in place. At least for 17.0.1 on ARC3.
@andreww
Copy link
Owner Author

andreww commented Apr 5, 2018

It looks like this should be possible. See travis-ci/travis-ci#4604, https://github.com/nemequ/icc-travis and https://docs.travis-ci.com/user/encryption-keys/ - I'll just need to create an encrypted intel serial number. Suspect I can get one of these from Advanced Research Computing at Leeds.

@andreww
Copy link
Owner Author

andreww commented Apr 5, 2018

See #55

@andreww
Copy link
Owner Author

andreww commented Apr 10, 2018

This would be really nice for #47. Opposite compiler bugs for Intel and PGI. Grrrr

@andreww andreww mentioned this issue Feb 14, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@andreww