-
Notifications
You must be signed in to change notification settings - Fork 50
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
{2023.06}[foss/2023a] GROMACS v2023.4 #463
Conversation
Instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
New job on instance
|
While I was debugging #401 interactively, I also tried installing 2023.4, and then that version did work fine. But now the build with the bot does show the same test failure again 😞
|
@bedroge Some time to blame |
It's using |
A unique subdirectory of |
I've tried building this version a few more times now, and it's failing all the time on that same test. For some reason, it worked the very first time, though 😕 |
@bedroge @boegel Gromacs v2023.4 works for NESSI: NorESSI#273 but with deb10 container on certain architectures. |
Oh, that's really interesting... Now we did have weird behaviour for both 2023.3 and 2023.4, where it occasionally does work, but for e.g. haswell it's failing (almost) all the time, I think. Doesn't look like NESSI builds for haswell (?), so maybe I can try doing that interactively with our old debian10 container. |
@TopRichard I tried it on a haswell node with our old Debian 10 build container (https://github.com/EESSI/filesystem-layer/pkgs/container/build-node/40951724?tag=debian10), but it has been stuck in the test step for several hours now, so I think it hangs (and we saw the same thing before). Is there any other significant difference in your Debian 10 container compared to the Debian 11 container? |
@bedroge we are using the same containers of EESSI , and our stack doesn’t have haswell, so that i try building GROMACS for haswell within NESSI stack, i will figure out a way to further help in this. |
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
Alternative formattings (edited manually):
Unable to download or merge changes between the source branch and the destination branch. or Unable to download or merge changes between the source branch and the destination branch.
Tip: This can usually be resolved by syncing your branch and resolving any merge conflicts. |
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
New job on instance
|
…-layer into gromacs_2023.4
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
New job on instance
|
This actually completed:
But then failed in the missing software check (I guess because the easyconfig hasn't been merged yet?):
So, let's try building for the other architectures as well. |
bot: build repo:eessi.io-2023.06-software arch:aarch64/generic |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
Quick summary of the status of the builds:
All the other ones actually completed successfully, but failed in the check for missing installations. Regarding the haswell build, I saw the following processes running on the node:
I'm guessing this may be a similar issue as what we are seeing in #508 and #456. |
Hi folks, I would like to use gromacs from the eessi prod repo. I understand this is the PR to generate gromacs in prod repo right? |
Hi @marconetto, yes, that's correct. Unfortunately, we're seeing weird test failures on a few CPU types, and these are quite hard to figure out. We'd really like to make GROMACS available, but we also really want to be sure that the builds are fine before we actually add them to the repository. So we'll keep working on them (we also have open PRs for version 2023.3 in #401 and 2024.1 in #499, but all with similar issues), and hopefully we will be able to resolve the issues soon. |
thanks @bedroge for the clarification! |
bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/haswell |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/haswell |
Updates by the bot instance
|
New job on instance
|
The haswell build is not getting stuck anymore (because of the Lmod hook that we added to the bot environment), but it does still fail due to one failing test:
This is the actual error message for the failing test:
|
superseded by #499 |
HI @marconetto, GROMACS 2024.1 is now available in the production repo. Does that version suit your needs, or did you have a specific need for version 2023.4? |
Hi @bedroge , this is great news! Thanks for you and your team by putting this together. This version is fine, thanks a lot! I will test it next week and let you know if something is not working as expected. |
No description provided.