Test Failure: Microsoft.Extensions.Configuration.Test.ConfigurationTests.OnChangeGetFiredForRelativeLinuxPath

[kg]

Summary:

File change watcher does not fire within timeout under JitStress on Linux ARM32 Docker.

Failed in (1):

• runtime-coreclr libraries-jitstress 20260409.1

Console Log: Console Log

Source: runtime-coreclr libraries-jitstress / net11.0-linux-Release-arm-no_tiered_compilation-(Debian.13.Arm32.Open)AzureLinux.3.Arm64.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-13-helix-arm32v7 / Microsoft.Extensions.Configuration.Test.ConfigurationTests.OnChangeGetFiredForRelativeLinuxPath

Failed tests:

- net11.0-linux-Release-arm-no_tiered_compilation-(Debian.13.Arm32.Open)AzureLinux.3.Arm64.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:debian-13-helix-arm32v7

  - Microsoft.Extensions.Configuration.Test.ConfigurationTests.OnChangeGetFiredForRelativeLinuxPath

Error Message:

System.Exception : on file change event handler did not get executed

Stack Trace:

   at Microsoft.Extensions.Configuration.Test.ConfigurationTests.WaitForChange(Func`1 test, String failureMessage, Int32 multiplier) in /_/src/libraries/Microsoft.Extensions.Configuration/tests/FunctionalTests/ConfigurationTests.cs:line 1001
   at Microsoft.Extensions.Configuration.Test.ConfigurationTests.WatchOverConfigJsonFileAndUpdateIt(String filePath) in /_/src/libraries/Microsoft.Extensions.Configuration/tests/FunctionalTests/ConfigurationTests.cs:line 1030
   at Microsoft.Extensions.Configuration.Test.ConfigurationTests.OnChangeGetFiredForRelativeLinuxPath() in /_/src/libraries/Microsoft.Extensions.Configuration/tests/FunctionalTests/ConfigurationTests.cs:line 1044

Analysis:

The test writes a config JSON file and waits for FileSystemWatcher to fire, but the event never fires within timeout. Ran on Linux ARM32 Docker (debian-13-helix-arm32v7 on azurelinux.3.arm64.open) under jitstress (TieredCompilation=0). FileSystemWatcher on Linux uses inotify which can be unreliable in Docker containers under resource pressure. Appears to be a flaky infrastructure/timing issue rather than a code bug.

• Generated by ci-pipeline-monitor/scripts/generate_report.py *

[dotnet-policy-service]

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

[dotnet-policy-service]

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

[tarekgh]

#111101