microsoft / microsoft/gctoolkit
"Concurrent phase not completely recorded" when processing CMS Unified log
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 177
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 3
Description
Describe the bug
When parsing the attached CMS log using the unified logger, no events are being recorded. Parser logging just reports a number of warnings: "Concurrent phase not completely recorded: 0"
Note that this may be a simple vs detailed logging issue: The attached log file does not contain any CPU lines for publishing to trigger off of. (I'll update this issue if I get logger parameters used)
To Reproduce
Parse the attached file.
Expected behavior
Log is parsed correctly and events are generated.
Affected File
gc_cms_no_events.zip
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 by parsing the attached gc_cms_no_events.zip with the unified logger and inspect the warnings about "Concurrent phase not completely recorded: 0." Done means the CMS log parses without that failure and generates events; confirm whether the missing CPU lines or logging mode affects the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100