Skip to content
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

Fixing CM-MLPerf automations broken by the newly released stripped-down version of CM (mlcflow) #1398

Closed
gfursin opened this issue Feb 13, 2025 · 1 comment

Comments

@gfursin
Copy link
Contributor

gfursin commented Feb 13, 2025

We have received reports that the recently introduced stripped-down version of CM for running MLPerf (mlcflow) has broken backward compatibility with many past CM projects and MLPerf submissions.

To resolve this issue, we are developing and testing CMX—a backward-compatible extension to CM—designed to maintain the functionality of existing CM-based projects and MLPerf submissions.

Our goal is to ensure continued support for all affected CM and MLPerf users.

@gfursin
Copy link
Contributor Author

gfursin commented Feb 14, 2025

After discussing the issue with my MLCommons colleagues, we decided to add a compatibility layer to CMX for the stripped-down version of CM (mlcflow for mlperf automations). This will enable seamless execution of past CM automations, new (extended) CMX automations, and simplified CM automations (mlcflow) through a unified CM/CMX interface. I will incorporate this layer in the next CMX release - this should resolve MLPerf compatibility issues for CM and CMX users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant