Skip to content

Keep fgDebugCheckUpdate function, remove only the stress mode check

54e6058
Select commit
Loading
Failed to load commit list.
Merged

Remove CHK_FLOW_UPDATE stress mode #122970

Keep fgDebugCheckUpdate function, remove only the stress mode check
54e6058
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis succeeded Jan 30, 2026 in 0s

.NET Result Analysis

Details

‼️ Build Analysis Check Result has been manually overridden

  • The build analysis check result has been updated by the user for the following reason: Known arm64 queue issues
  • The check result has changed from Failure to Success

Tip

To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.

⚠️ The following pipeline(s) will not be analyzed as has been explicited excluded from analysis

Known Infrastructure Errors

Build Failures

runtime / Build / windows-arm64 Release NativeAOT

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌The job running on agent NetCore-Public 513 ran longer than the maximum time of 180 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

runtime / Build / windows-arm64 Release NativeAOT_Libraries

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌The job running on agent NetCore-Public 517 ran longer than the maximum time of 240 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

runtime / Build / coreclr Pri0 Runtime Tests Run windows arm64 checked

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌The job running on agent NetCore-Public 165 ran longer than the maximum time of 300 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

2 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [runtime] [runtime-dev-innerloop] [runtime]

Known test errors

Test Failures (11 tests failed)

🔹 [All failing tests from runtime]

Was this helpful? Yes No