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.

Sign up for GitHub

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

Jump to bottom

User feedback: adding MLCommons CM version in MLPerf submission #1071

Closed
gfursin opened this issue Jan 27, 2024 · 3 comments
Closed

User feedback: adding MLCommons CM version in MLPerf submission #1071

gfursin opened this issue Jan 27, 2024 · 3 comments
Assignees
@arjunsuresh @gfursin

Comments

@gfursin
Copy link
Contributor

gfursin commented Jan 27, 2024

Following #1052, we got a feedback to add CM version in MLPerf submissions, i.e. "Automated by MLCommons CM v1.6.0".
@gfursin
Copy link
Contributor Author

gfursin commented Jan 29, 2024

@arjunsuresh - an extra request: on Windows we generate a multi-line command to rerun MLPerf inference via CM, however we use Linux separator \ at the end of the line. we should use ^ on Windows ...

@gfursin
Copy link
Contributor Author

gfursin commented Jan 29, 2024

Another feedback that we got: we need to detect hashes of pulled Git repos via CM (such as MLPerf inference) and add these flags to the generated CM command in MLPerf readme ...

gfursin added a commit to ctuning/mlcommons-ck that referenced this issue Feb 12, 2024
@gfursin
added host info in MLPerf result readmes: mlcommons#1071
9e2e0bc
@gfursin
Copy link
Contributor Author

gfursin commented Feb 12, 2024

Fixed

@gfursin gfursin closed this as completed Feb 12, 2024
arjunsuresh pushed a commit to mlcommons/cm4mlops that referenced this issue May 1, 2024
@gfursin
added host info in MLPerf result readmes: mlcommons/ck#1071
c47d0ec
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arjunsuresh arjunsuresh

@gfursin gfursin

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arjunsuresh @gfursin