-
Notifications
You must be signed in to change notification settings - Fork 66
{2023.06}[2023a] MrBayes #1157
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] MrBayes #1157
Conversation
Signed-off-by: laraPPr <[email protected]>
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws |
|
New job on instance
|
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:zen2 |
|
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
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws arch:aarch64/generic |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
The build on A64FX is taking a while because a bunch of dependencies for I just checked the process in the job, and the build for For MrBayes itself, it's not that bad: So we can just wait it out a bit longer, see what happens on A64FX before making a move (if anything fail there, we'll definitely divert to another PR). |
|
Actually the fact that only 4 cores are used for the A64FX builds points to a problem, see: |
|
The build on A64FX of Octave + MrBayes actually worked, but the installation was marked as failed because of a missing dependency This was fixed for other CPU targets in #976, but not for A64FX. I think we can proceed with just deploying for the fully supported CPU targets, and get back to closing the gap for A64FX in subsequent PRs... @laraPPr Do you agree? |
|
Yes, good for me I triggered it without thinking and than I was also interested in seeing how far it got. |
|
Deploy wasn't actually triggered for AWS bot, because the event was never received because smee service was down at the time... |
|
Staging PR merged, so deploy is under way... |
No description provided.