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

Whenever CM script fails because of some wrapped code (such as MLPerf inference), add support in meta where to report an error #1185

Closed
gfursin opened this issue Mar 27, 2024 · 2 comments
Closed

Whenever CM script fails because of some wrapped code (such as MLPerf inference), add support in meta where to report an error #1185

gfursin opened this issue Mar 27, 2024 · 2 comments
Assignees
@gfursin
Labels
enhancement

Comments

@gfursin
Copy link
Contributor

gfursin commented Mar 27, 2024

We got a feedback from CM users that when some tool/library fails when wrapped by a CM script, it can be useful to provide a link to a repository of that tool to report an error to let the authors reproduce and fix an error...

Maybe we can add a key "url_to_report_error" for that ...
@gfursin gfursin self-assigned this Mar 27, 2024
@gfursin
Copy link
Contributor Author

gfursin commented Mar 28, 2024

We may also want to automatically dump versions of all deps resolved by CM and system info ...

@gfursin
Copy link
Contributor Author

gfursin commented Apr 28, 2024

I added --repro to dump lost of debug info to cm-repro directory. I moved this ticket to mlcommons@cm4mlops.

@gfursin gfursin closed this as completed Apr 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gfursin gfursin

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gfursin