-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update structured logger #75865
Update structured logger #75865
Conversation
Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.
@@ -319,7 +319,7 @@ | |||
Infra | |||
--> | |||
<PackageVersion Include="Microsoft.Win32.Registry" Version="5.0.0" /> | |||
<PackageVersion Include="MSBuild.StructuredLogger" Version="2.2.169" /> | |||
<PackageVersion Include="MSBuild.StructuredLogger" Version="2.2.386" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<PackageVersion Include="MSBuild.StructuredLogger" Version="2.2.386" /> | |
<PackageVersion Include="MSBuild.StructuredLogger" Version="2.2.350" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why that version vs. latest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But I don't know whether 350 is new enough to resolve the original issue
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like rerun of the CI made the error go away. Interesting.
Backports #75865 to fix Correctness_Build_Artifacts CI.
Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.
Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.
Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.
Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.