ET & KT merge through chakra_trace_link (ET+) does not contain timing information
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 196
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Describe the Bug
I am using chakra_trace_link for merging ET & KT generated for a resnet workload ( single image) however I do not see any timing information in ET+ file.
Script completes without any errors or warnings
Steps to Reproduce
-
chakra_trace_link --pytorch-et-file "et_file_path" --kineto-file "kineto_file_path" --output-file "merged_file_path"
-
"schema": "1.0.2-chakra.0.0.4"
-
this was tried on a machine having H100
Expected Behavior
ET+ file to have timing information fetched from Kineto Trace.
Screenshots
attached screenshot showing script completion without any errors.
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_trace_link entry point and reproduce the command using the PyTorch ET file and Kineto file described in the issue. Trace the merge output and compare it with the Kineto timing data; the work is done when the generated ET+ file contains the expected timing information and the command still completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100