Skip to content

added new Cray* toolchain versions with dependency pinning#2222

Merged
boegel merged 4 commits intoeasybuilders:developfrom
gppezzi:craygnu_xc
Jan 22, 2016
Merged

added new Cray* toolchain versions with dependency pinning#2222
boegel merged 4 commits intoeasybuilders:developfrom
gppezzi:craygnu_xc

Conversation

@gppezzi
Copy link
Copy Markdown
Contributor

@gppezzi gppezzi commented Dec 14, 2015

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

@hpcugentbot
Copy link
Copy Markdown

Automatic reply from Jenkins: Can I test this?

@boegel
Copy link
Copy Markdown
Member

boegel commented Dec 14, 2015

Jenkins: ok to test

@boegel boegel added this to the v2.5.0 milestone Dec 14, 2015
@hpcugentbot
Copy link
Copy Markdown

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.

@hpcugentbot
Copy link
Copy Markdown

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.

@boegel boegel modified the milestones: v2.6.0, v2.5.0 Dec 15, 2015
@gppezzi gppezzi changed the title added new CrayGNU toolchain version with dependency pinning added new Cray* toolchain versions with dependency pinning Dec 18, 2015
@hpcugentbot
Copy link
Copy Markdown

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.

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Dec 18, 2015

Test report by @gppezzi
SUCCESS
Build succeeded for 12 out of 12 (12 easyconfigs in this PR)
Linux SLES 11_SP3, Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz, Python 2.7.7
See https://gist.github.com/7fb936ce407b0d1bd61b for a full test report.

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Dec 18, 2015

Test report by @gppezzi
SUCCESS
Build succeeded for 12 out of 12 (12 easyconfigs in this PR)
Linux SLES 11_SP3, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.7.6
See https://gist.github.com/0a3ee80209310ac02651 for a full test report.

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Jan 18, 2016

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

@pforai
Copy link
Copy Markdown
Contributor

pforai commented Jan 18, 2016

@gppezzi Individual TC PRs is fine, each with a matching HPL config that builds with that would be ideal.

@boegel
Copy link
Copy Markdown
Member

boegel commented Jan 18, 2016

@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 HPL easyconfigs are pretty much a no-brainer since they're (near) identical to each other but also to existing HPL easyconfigs (only exception is the extra patch in the CCE ones).

The others are simple enough to review in a single PR, since it's basically just a matter of the toolchain definition.

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Jan 21, 2016

Test report by @gppezzi
SUCCESS
Build succeeded for 12 out of 12 (12 easyconfigs in this PR)
Linux SLES 11_SP3, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.7.6
See https://gist.github.com/27a760d46e7dfb24ed23 for a full test report.

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Jan 21, 2016

Test report by @gppezzi
SUCCESS
Build succeeded for 12 out of 12 (12 easyconfigs in this PR)
Linux SLES 11_SP3, Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz, Python 2.7.7
See https://gist.github.com/0beca8c3b1462ee1645f for a full test report.

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Jan 21, 2016

@pforai It would be great if you could test these easyconfigs (using easyblock from #766) on any other Cray site...

Of course it is only expected to work out of the box if they have the PEs from 2015.06 and 2015.11 installed.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

you're missing a version-fixed intel here

@hpcugentbot
Copy link
Copy Markdown

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.

@boegel
Copy link
Copy Markdown
Member

boegel commented Jan 22, 2016

@gppezzi: does it makes sense to use the same intel version in both 2015.06 and 2015.11?

Also, can you submit a new test report? Just for CrayIntel is fine, but I guess a full one is easier. ;)

@boegel
Copy link
Copy Markdown
Member

boegel commented Jan 22, 2016

@pforai: ping on a test report for this on non-CSCS Cray systems?

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Jan 22, 2016

@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

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Jan 22, 2016

Test report by @gppezzi
SUCCESS
Build succeeded for 12 out of 12 (12 easyconfigs in this PR)
Linux SLES 11_SP3, Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz, Python 2.7.7
See https://gist.github.com/ee653dbbe01c9dd85df7 for a full test report.

@gppezzi
Copy link
Copy Markdown
Contributor Author

gppezzi commented Jan 22, 2016

Test report by @gppezzi
SUCCESS
Build succeeded for 12 out of 12 (12 easyconfigs in this PR)
Linux SLES 11_SP3, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.7.6
See https://gist.github.com/4737cfb98962bba09408 for a full test report.

@boegel
Copy link
Copy Markdown
Member

boegel commented Jan 22, 2016

Despite some concerns w.r.t. the intel version used in the CrayIntel toolchain, this is good to go.

Thanks a lot for working on this @gppezzi, this is a huge step towards stable Cray support (cfr. easybuilders/easybuild-framework#1390)!

boegel added a commit that referenced this pull request Jan 22, 2016
added new Cray* toolchain versions with dependency pinning
@boegel boegel merged commit f504448 into easybuilders:develop Jan 22, 2016
@pforai
Copy link
Copy Markdown
Contributor

pforai commented Jan 27, 2016

Test report by @pforai
FAILED
Build succeeded for 4 out of 12 (12 easyconfigs in this PR)
Linux SLES 11_SP3, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.6.9
See https://gist.github.com/bdce401c48fa3d4ee2d6 for a full test report.

@pforai
Copy link
Copy Markdown
Contributor

pforai commented Jan 27, 2016

Test report by @pforai
FAILED
Build succeeded for 9 out of 12 (12 easyconfigs in this PR)
Linux SLES 11_SP3, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.6.9
See https://gist.github.com/650e5060c847e6e50142 for a full test report.

@boegel
Copy link
Copy Markdown
Member

boegel commented Jan 27, 2016

@pforai: what's going on with the failed reports? Is that the swap issue for all toolchain deps?

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.

4 participants