-
Notifications
You must be signed in to change notification settings - Fork 702
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.
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
{chem}[foss/2020b] Dalton v2020.0 #13921
Conversation
…make path is also incorrect
…onfigs into dalton
@LHurst-JM: Tests failed in GitHub Actions, see https://github.com/easybuilders/easybuild-easyconfigs/actions/runs/1208994440
bleep, bloop, I'm just a bot (boegelbot v20200716.01) |
@boegelbot please test @ generoso |
@verdurin: Request for testing this PR well received on login1 PR test command '
Test results coming soon (I hope)... - notification for comment with ID 917988119 processed Message to humans: this is just bookkeeping information for me, |
Test report by @boegelbot |
Checksum failed on the source. That's definitely the checksum for the source that was used in my testing:
Upstream have not changed the commit the tag points to:
So I'm not sure why the checksum is different. I'll delete and re-download the source with --fetch... |
Somehow the source checksum has changed upstream since I uploaded the easyconfig. The tag still points to the same commit, so I really don't understand why?:
|
Is there any reason not to use one of the upstream tarballs instead, e.g. https://gitlab.com/dalton/dalton/-/archive/Dalton2020.0/dalton-Dalton2020.0.tar.bz2 ? |
Only that I did not know they existed ;) Upstream's website's download link takes you to the 'release/2020' branch HEAD, which is under active development (and therefore unsutable to use as the source). The tag seems stable and this is exactly how Dalton-2016-intel-2017b-i8.eb, which is the only version currently in EB, fetches it. I'm still very confused by the tag, which allegedly hasn't changed in 10 months, suddenly resulting in a different checksum for the clones source. Happy to try the one of those archive links instead. |
...so that results in a file with yet another checksum:
(via the releases page, which claims this source file is the same commit as the tag) 🤦 |
Also you need recursive download here to get the full functionality and can thus not use the simple tarball. |
# 'runtests' | ||
buildopts = "&& ctest --output-on-failure -L dalton" | ||
|
||
separate_build_dir = True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is default for CMakeMake and can be removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't work without this (-L dalton
) in my environment?
This is based on how other CMakeMake easyconfigs work.
You don't if you seperate the extrenal dependencies into their own ebs. |
Yes, that would be preferable, splitting the submodules out that is, but I haven't had time to look at that... Also look at #14154 and #14158 I'm currently running that one with tests on broadwell and zen2 |
I get the same error on my zen2 system that you saw with my foss-2021a build. |
And see the #14158 for the final details on how to run the tests and the required patches. |
closing this since see also: |
Bump of Dalton from 2016 to 2020.0 and build for foss-2020b (only other version in easybuild is for intel-2017b).
Dalton's new (python) configure command seems to fix the issues that needed a lot of patches in 2016.
N.B. This eb takes between 3 and 4.5 hours to build on my cluster (on each of 44-core Skylake, 60-core Zen and 120-core Zen2 nodes). Most of that time is spent running the test suite. One test fails on Zen2 due to upstream bug - https://gitlab.com/dalton/dalton/-/issues/183