[ci-scan] Test failure: jitstress2 JIT assert 'Missing BBF_PROF_WEIGHT flag' in fgprofile.cpp crashes DependencyInjection.Tests

[github-actions]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1603514
Build error leg or test failing: linux-x64 Release-Microsoft.Extensions.DependencyInjection.Tests

KBE authoring guidance (ci-failure-scan)

• Error Details is for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.
• Build Analysis parses only the single JSON block under Error Message.
• ErrorMessage is a case-sensitive ordinal String.Contains substring copied verbatim from the failing log.
• Set BuildRetry to true only for a clear infrastructure retry case. ExcludeConsoleLog disables Helix console-log scanning.

Error Details

Under DOTNET_JitStress=2 (jitstress2_tiered) on the libraries-jitstress pipeline, the JIT hits an assertion while compiling ServiceProviderEngineScope.DisposeAsync, aborting the Microsoft.Extensions.DependencyInjection.Tests work item with exit code 134 (SIGABRT). Reproduced across multiple linux/windows legs:

DOTNET_JitStress=2
Assert failure(PID 2331 [0x0000091b], Thread: 2361 [0x0939]): Assertion failed '!"Missing BBF_PROF_WEIGHT flag"' in 'Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope:DisposeAsync():this' during 'Transform async' (IL size 163; hash 0x1af815f2; Instrumented Tier0)
    File: /__w/1/s/src/coreclr/jit/fgprofile.cpp:4932
exit code 134 means SIGABRT Abort.

Stable and recurring: observed in source build 1603514 (2026-09-19) and follow-up build 1604101 (2026-09-20), with the same assertion and JIT source location.

Error Message

{
  "ErrorMessage": "Assertion failed '!\"Missing BBF_PROF_WEIGHT flag\"' in 'Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope:DisposeAsync():this'",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Agentic workflow metadata (ci-failure-scan)

Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 1 hits in failure.log

---

Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.

Generated by CI Outer-Loop Failure Scanner · opus48 · 831.7 AIC · ⌖ 14.9 AIC · ⊞ 19.2K · ◷

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[jakobbotsch]

Duplicate of #134295