-
Notifications
You must be signed in to change notification settings - Fork 3
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
LAMMPS: try to Build OBMD package on arm #16
Conversation
Instance
|
bot: build arch:aarch64/neoverse_n1 |
Updates by the bot instance
|
New job on instance
|
From the slurm log:
|
Ah that is not the error I was seeing. weird normally it should be set correctly in the easyBlock |
Or I broke in this pr https://github.com/easybuilders/easybuild-easyblocks/pull/3485/files |
Pedro can you tell what is in the output here /tmp/eb-w_sv3q0o/eb-9pov_lx4/easybuild-run_cmd-c69cx09o.log |
Seems like archspec is returning something else (
|
Ah yes because this is an arm instance on Azure so it has different flags than the amazon neoverse_n1. Ok so this is not gonna help me further with trying to debug laraPPr/lammps#3. Than maybe I'll just do it interactively on the amazon cluster to see if I can reproduce it their. But @ocaisa is probably interested in this case. @casparvl are we testing the ReFrame test-suite (and by extention LAMMPS) on an arm instance on Azure? Maybe we should also set up the test-suite on this cluster? |
I see we've never rescheduled the cronjob after moving to the new cluster. Done so now. The Reframe config already contained the neoverse_n1 node, so it's pretty simple to also run tests there. I've scheduled a new cronjob that should run on both zen4 and neoverse_n1. For now, I seem to have a job stuck in CF state for the past 27 minutes, so I can't properly verify if this runs now work, but I don't see any reason why not. |
@casparvl did the LAMMPS test pass with the test-suite on the arm azure instance? |
Features cortex-a72: Features neoverse_n1: |
Yep:
|
bot: build arch:aarch64/neoverse_n1 |
Updates by the bot instance
|
New job on instance
|
bot: build arch:x86_64/amd/zen4 |
Updates by the bot instance
|
New job on instance
|
neoverse_n1 build is now working with the new easyblock
|
Failed because of a missing patch file in the easyconfig |
bot: build arch:aarch64/neoverse_n1 |
Updates by the bot instance
|
New job on instance
|
@Neves-P the same error of zen4 were seeing here multixscale/dev.eessi.io-lammps-plugin-obmd#2 is also here |
This was just to test arm builds before multixscale/dev.eessi.io-lammps was set up. Can close this now. |
PR merged! Moved |
No description provided.