-
Notifications
You must be signed in to change notification settings - Fork 75
{2023.06}[2023a] acpype v2023.10.27 #1332
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
base: main
Are you sure you want to change the base?
Conversation
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
AmberTools 23.6 is picking up the wrong Python: |
c528fa1 to
79112a9
Compare
79112a9 to
ef843c4
Compare
easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-5.2.0-2023a.yml
Outdated
Show resolved
Hide resolved
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-5.2.0-2023a.yml
Outdated
Show resolved
Hide resolved
…23a.yml Co-authored-by: Caspar van Leeuwen <33718780+casparvl@users.noreply.github.com>
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen3 |
|
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
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
This build seems to hang on all ARM architectures. In a 1381 minutes of CPU time, that's almost the full 23:23h this job has now been running. |
|
This is almost certainly the test step, I also see a process: |
|
Ran a few |
|
Also, for 125692, I downright killed easybuild. I hope I can still get access to the temporary log file... |
|
Hm... log file just says: Nothing more. Not very useful. |
|
bot:cancel 125690,125691 |
|
bot:cancel 14401394 |
|
I remember |
|
bot:cancel jobid:14401394 |
Yeah, I'm pretty sure this is a real hang. I think the best way to investigate is a build with |
I guess i can get an interactive shell on the AWS build cluster as i did for the QE benchmarks and test from there |
|
Curios if it could be something similar to http://archive.ambermd.org/201606/0163.html (@boegel ) |
No description provided.