Skip to content

Fix MECFG test race when checking token fired too soon. - #135918

Open
mrek-msft wants to merge 2 commits into
dotnet:mainfrom
mrek-msft:dev/mrek/mecfg-test-tokenfire-race
Open

mrek-msft wants to merge 2 commits into
dotnet:mainfrom
mrek-msft:dev/mrek/mecfg-test-tokenfire-race

Conversation

@mrek-msft

Copy link
Copy Markdown
Member

Fix #135612

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@dotnet-policy-service

Copy link
Copy Markdown
Contributor

Tagging subscribers to this area: @dotnet/area-extensions-configuration
See info in area-owners.md if you want to be subscribed.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🟢 Approval recommended

The bounded, test-only waits preserve existing assertions and introduce no blocking issues.

1 open finding
What changed in this PR

Addresses the configuration reload test race reported in #135612 without changing production behavior.

Changes:

  • Waits for reload tokens alongside expected configuration values.
  • Adds a token wait to the reload-error test.

Validation was limited to source inspection; no builds or tests were run.

File Description
src/​libraries/​Microsoft.Extensions.Configuration/​tests/​FunctionalTests/​ConfigurationTests.cs Waits for reload notifications before asserting token state.

🧠 Review effort: Balanced

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Test failure: Microsoft.Extensions.Configuration.Test.ConfigurationTests.CreatingWritingDeletingCreatingFileWillReload

3 participants