Evaluation started / ended events do not get logged in file / console loggers
- Dominant language
- C#
- Stars
- 5.5k
- Forks
- 1.5k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 133
Description
### Steps to reproduce
```
dotnet new console
dotnet msbuild /fl /flp:vebosity=diagnostic /clp:verbosity=diagnostic > out
```
### Expected behavior
out and msbuild.log contain evaluation started / ended events which wrap around the events coming from that evaluation (evaluation events get indented one level deeper under the evaluation started / ended events)
### Actual behavior
The log files do not contain these events
### Cause
It seems the FileLogger does not log all events, it treats each event type separately. The evaluation started / ended events slip through the cracks and do not get logged. The binary logger does write them out, because it does not discriminate on the event type.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the issue with the provided dotnet new console and dotnet msbuild commands, then inspect the FileLogger event handling and compare it with the binary logger behavior. Done means file and console logs include evaluation started and ended events, with evaluation events indented beneath them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100