Reduce logging verbosity in GrpcSidecarFixture for organized test output#581
Closed
Reduce logging verbosity in GrpcSidecarFixture for organized test output#581
Conversation
…ganized Co-authored-by: YunchuWang <12449837+YunchuWang@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Investigate and fix test failure in CI pipeline
Reduce logging verbosity in GrpcSidecarFixture for organized test output
Dec 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI test logs in Grpc.IntegrationTests were unreadable due to verbose ASP.NET Core/gRPC infrastructure logging drowning out actual test output. The original test failure from PR #551 was already fixed by PR #579.
Changes
GrpcSidecarFixturelogging to filter out noisy infrastructure logs:WarningMicrosoft.DurableTask.Sidecar:Information(orchestration events)Microsoft.Hosting.Lifetime:Information(app lifecycle)Before/After
Before: Every gRPC request logged 4+ lines of routing/hosting diagnostics
After: Only relevant sidecar events (instance creation, orchestration completion, errors)
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.