Skip to content
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

Merged
merged 1 commit into from
Nov 12, 2024
Merged

Update structured logger #75865

merged 1 commit into from
Nov 12, 2024

Conversation

jaredpar
Copy link
Member

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.
@jaredpar jaredpar requested a review from a team as a code owner November 12, 2024 04:01
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 12, 2024
@@ -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" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<PackageVersion Include="MSBuild.StructuredLogger" Version="2.2.386" />
<PackageVersion Include="MSBuild.StructuredLogger" Version="2.2.350" />

Copy link
Member Author

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because of this error:
image

Copy link
Member

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

Copy link
Member

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.

@jjonescz jjonescz enabled auto-merge (squash) November 12, 2024 12:47
@jjonescz jjonescz merged commit 5780d35 into main Nov 12, 2024
28 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Nov 12, 2024
@jjonescz jjonescz deleted the dev/jaredpar/logger branch November 12, 2024 13:48
JoeRobich added a commit that referenced this pull request Nov 21, 2024
Backports #75865 to fix
Correctness_Build_Artifacts CI.
@jjonescz jjonescz modified the milestones: Next, 17.13 P2 Nov 25, 2024
jjonescz pushed a commit to jjonescz/roslyn that referenced this pull request Nov 25, 2024
Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.
jjonescz pushed a commit to jjonescz/roslyn that referenced this pull request Nov 25, 2024
Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.
jjonescz added a commit that referenced this pull request Nov 26, 2024
* Workaround failing official builds (#75898)

* Update structured logger (#75865)

Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.

---------

Co-authored-by: Jared Parsons <jared@paranoidcoding.org>
jjonescz pushed a commit that referenced this pull request Nov 27, 2024
Upgrade to latest structured logger binaries and see if that addresses the failure to read binary logs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants