-
Notifications
You must be signed in to change notification settings - Fork 52
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}[2023a] Modflow 6.4.4 and deps #522
Conversation
Instance
|
Yes, once we can use the bot again... :) |
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
New job on instance
edit (by @boegel): I cancelled job 8917, tests were hanging |
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/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
|
#522 (comment) was hanging in one of the tests from PETSc:
However, a build on I've triggered builds for all of the other architectures, including a rebuild on |
easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.9.0-2023b.yml
Outdated
Show resolved
Hide resolved
I had a quick look at the build logs, as I was curious why the haswell build took so much longer than the others. It turns out that the both the build and test step of PETSc contain a lot of tests, and though quite a lot fail for all targets, the situation on haswell is much worse due to timeouts.
So something doesn't seem right here. I suspect that it may be related to the MPI issues on haswell that we've been observing for other PRs/builds as well. |
Just to log this: as discussed on Slack, Bob will manually put an LMOD hook in place for the bot in it's
Essentially this mimics what was done on |
bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/haswell |
Updates by the bot instance
|
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/intel/haswell |
Updates by the bot instance
|
New job on instance
|
With the Lmod hook in place, the haswell build took about as long as for the other CPU targets. The number of failing / timed out tests is also very similar to the other ones:
|
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.
I'm seeing similar test results for the PETSc installations on our local cluster and on EB's generoso cluster, so I'm assuming this is "normal".
Depends on: