-
Notifications
You must be signed in to change notification settings - Fork 66
{2023.06}[gfbf/2023a,gfbf/2023b] MLflow 2.10.2, MLflow 2.18.0 #1188
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
Conversation
PetrKralCZ
commented
Sep 10, 2025
|
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
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/generic |
|
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
|
|
Build on A64FX is worth a try, since there's not too much stuff missing relative to the fully supportrd CPU targets: and |
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-deucalion for:arch=aarch64/a64fx |
|
New job on instance
|
|
Failing sanity check for Build of Not going to pursue this for now, shouldn't block the deployment of MLflow for all fully supported CPU targets. |
boegel
left a comment
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.
lgtm
I tried building this interactively and could reproduce it with EESSI-extend. It was able to solve it by pointing edit: confirmed it interactively, rebuilding Python with that fix solves the issue: PR to fix this: #1191. |