Converting to Chakra Execution Trace with chakra_converter failed with unsupported schema version '1.0.1'.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 196
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Describe the Bug
We followed instructions on the following wiki page: https://github.com/mlcommons/chakra/wiki/Chakra-Execution-Trace-Collection-%E2%80%90-A-Comprehensive-Guide-on-Merging-PyTorch-and-Kineto-Traces.
We've captured pytorch traces and kineto traces, and the "Merging Traces with chakra_trace_link" step also went well. However, when we tried to convert the merged trace to chakra trace, we encountered the following issue:
ValueError: Unsupported schema version '1.0.1'. Please check if the schema version is in the list of supported versions: ['1.0.2-chakra.0.0.4', '1.0.3-chakra.0.0.4', '1.1.0-chakra.0.0.4', '1.1.1-chakra.0.0.4']. The schema version of the trace is not supported by the converter. The schema version is determined by the PyTorch version used to collect Chakra host execution traces. Please consider changing the PyTorch version you are using. For more details, you can follow the git history of the relevant file: https://github.com/pytorch/pytorch/blob/7cd48df2dae7e2194438b162968c47d1f05bf20e/torch/csrc/profiler/standalone/execution_trace_observer.cpp#L308. Check which PyTorch versions generate Chakra host traces that are supported by the converter.
Steps to Reproduce
Steps to reproduce the behavior.
Please include the version information where the bug was observed.
Expected Behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the chakra_converter conversion path and the supported schema-version list shown in the error. Compare those versions with the PyTorch execution_trace_observer.cpp history linked in the report, then reproduce conversion using a trace generated by the affected PyTorch version. Done means the converter either supports schema version 1.0.1 or clearly rejects it with documented compatible PyTorch versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100