added new Cray* toolchain versions with dependency pinning#2222
added new Cray* toolchain versions with dependency pinning#2222boegel merged 4 commits intoeasybuilders:developfrom
Conversation
|
Automatic reply from Jenkins: Can I test this? |
|
Jenkins: ok to test |
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/5285/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/5287/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/5393/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
|
Test report by @gppezzi |
|
Test report by @gppezzi |
|
@boegel please let me know how to proceed, if you prefer that I make separate PRs for each toolchain or not (the .eb are very similar, there are only a few differences on the dependencies) |
|
@gppezzi Individual TC PRs is fine, each with a matching HPL config that builds with that would be ideal. |
|
@gppezzi: I wouldn't bother splitting this up, it's not really going to help much (if anything, it'll add more overhead, for the both of us) The general rule-of-thumb is to keep easyconfig PRs below 10 new easyconfigs. This is kind of an exception, since the easyconfigs are so similar to each other (in two groups). The others are simple enough to review in a single PR, since it's basically just a matter of the toolchain definition. |
|
Test report by @gppezzi |
|
Test report by @gppezzi |
There was a problem hiding this comment.
you're missing a version-fixed intel here
|
Easyconfigs unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/5773/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
@gppezzi: does it makes sense to use the same Also, can you submit a new test report? Just for |
|
@pforai: ping on a test report for this on non-CSCS Cray systems? |
|
@boegel the intel version didn't seem to change from June to November. the release notes don't mention the minor version they provide and this is the only one from the 15 series we have. (Release notes from may still suggested to use 14.x but not in June) Test report is on the way |
|
Test report by @gppezzi |
|
Test report by @gppezzi |
|
Despite some concerns w.r.t. the Thanks a lot for working on this @gppezzi, this is a huge step towards stable Cray support (cfr. easybuilders/easybuild-framework#1390)! |
added new Cray* toolchain versions with dependency pinning
|
Test report by @pforai |
|
Test report by @pforai |
|
@pforai: what's going on with the failed reports? Is that the |
This PR adds eb files for the new CrayGNU, CrayIntel and CrayCCE toolchains (with dep. pinning). For validation, it adds also easyconfig files for HPL.
Requires: EB 2.5.0 and hpcugent/easybuild-easyblocks/pull/766