Profilee STDOUT: GetObjectGeneration failed hr=0x80131389
Profilee STDOUT: PROFILER TEST FAILED
Test failed: Profiler tests are expected to contain the text 'PROFILER TEST PASSES' in the console output of the profilee app to indicate a passing test. ... This text was not found in the output above. Profilee returned exit code 100.
at Profiler.Tests.ProfilerTestRunner.FailFastWithMessage(String error)
Failed test: profiler/runtimeasyncapis/runtimeasyncapis/runtimeasyncapis.cmd
{
"ErrorMessage": "Failed test: profiler/runtimeasyncapis/runtimeasyncapis",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1567889
Build error leg or test failing: coreclr Pri0 Runtime Tests Run R2R_CG2 (all platforms) - profiler/runtimeasyncapis
KBE authoring guidance (ci-failure-scan)
Error Detailsis for readers. Paste the full exception, stack trace, or build error excerpt so the failure is understandable without opening the raw log.Error Message.ErrorMessagearray elements each match one log line in order; copied verbatim from the failing log.BuildRetrytotrueonly for a clear infrastructure retry case.ExcludeConsoleLogdisables Helix console-log scanning.Error Details
The
profiler/runtimeasyncapistest fails under the crossgen2 R2R_CG2 (and R2R_CG2_HotColdSplitting) legs across all platforms (Windows x64/arm64, Linux x64/arm64, macOS x64/arm64). The profilee repeatedly logsGetObjectGeneration failed hr=0x80131389(COR_E_INVALIDOPERATION) and never printsPROFILER TEST PASSES, so the runner fails the test. This is a fresh regression in the runtime-coreclr crossgen2 pipeline: builds through 2026-08-25 passed; builds from 2026-08-26 (source #1567889) through the 2026-08-27 follow-up #1569780 fail, with 39 failed Helix work items in each.Error Message
{ "ErrorMessage": "Failed test: profiler/runtimeasyncapis/runtimeasyncapis", "ErrorPattern": "", "BuildRetry": false, "ExcludeConsoleLog": false }Agentic workflow metadata (ci-failure-scan)
Workflow artifact: ci-failure-scan
Artifact kind: kbe-verification
Verified match count: 2 hits in failure.log
Filed by
ci-failure-scan(detection only).ci-failure-fixwalks open[ci-scan]KBEs and either opens a small fix PR or comments here to loop in owners — it never disables the test.Note
This issue was generated by an AI agent (GitHub Copilot / ci-failure-scan workflow).
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
dotnet.github.ioTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
Report
Summary
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1567889
Error message validated:
[Failed test: profiler/runtimeasyncapis/runtimeasyncapis]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/28/2026 7:49:45 AM UTC
Report
Summary
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1567889
Error message validated:
[Failed test: profiler/runtimeasyncapis/runtimeasyncapis]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/28/2026 7:49:45 AM UTC