[unitrace] [bug] unitrace produces corrupted json trace for samples cl_gemm/ze_gemm
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- observability-sre
Research direction
Reproduce by running unitrace with --opencl --call-logging --chrome-kernel-logging -o ze_gemm.json on the cl_gemm or ze_gemm sample, then open the output and find where the JSON breaks. The issue suggests stray program output is written into the trace file, so look for stdout or printf writes on the path that emits the Chrome trace. Done when the generated ze_gemm.json parses as valid JSON.
Written by the indexing model from the issue text.
Description
Collection CLI:
unitrace --opencl --call-logging --chrome-kernel-logging -o ze_gemm.json .../ze_gemm
Produces corrupted json trace file:
Probably some output goes into trace file.
- Dominant language
- C++
- Stars
- 276
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from intel/pti-gpu
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
[unitrace] Do not fetch for 3rd party projects 1) at build stage, 2) if they are already installedOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
enhancement question
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DarkStarSystems/pcons#224 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
LizardByte/Sunshine#5953 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
(S1 - Need confirmation)
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
CleverRaven/Cataclysm-DDA#89133 ·
Maintainers usually reply within 1 day