[ci-scan] Skip PInvokeUnhandled under interpreter (refs #128899)

[github-actions]

Reasoning

The PInvokeUnhandled test consistently hits a native assert (GetRegdisplaySP(m_crawl.pRD) == (TADDR)pICF->GetCallSiteSP()) in the runtime-interpreter pipeline (definition 316). This is a consistency check in the stack walker that fires when running under the interpreter because the interpreter's frame layout differs from JIT-compiled code. Marking the test InterpreterIncompatible is the correct fix as the test exercises P/Invoke exception handling which is not compatible with the interpreter's stack frame representation.

Linked KBE: #128899

Match verification (from Step 4.8):

1. Same test/family: yes — PInvokeUnhandled in baseservices/exceptions
2. Same failure signature: yes — GetRegdisplaySP consistency assert
3. Same OS: yes — windows
4. Same architecture: yes — x64

Impact on platforms

• runtime-interpreter (def 316) windows-x64 checked, exit code -1073740286 (STATUS_FAIL_FAST_EXCEPTION)

Errors log

Assert failure: Consistency check failed:
FAILED: (GetRegdisplaySP(m_crawl.pRD) == (TADDR)pICF->GetCallSiteSP()) || (GetFP(m_crawl.pRD->pCurrentContext) == pICF->GetCalleeSavedFP())
Failed test: baseservices/exceptions/UnhandledExceptionHandler/PInvoke/PInvokeUnhandled/PInvokeUnhandled.cmd
Expected: 100
Actual: -1073740286

First build it occurred

• Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1440788
• Finished: 2026-05-29T22:51:55Z
• Occurrences in window: 2+ (persistent across multiple consecutive builds)

Linked issue

• [ci-scan] Test failure: PInvokeUnhandled assert in runtime-interpreter (GetRegdisplaySP) #128899

---

Filed by ci-failure-scan, which scans dnceng-public outer-loop pipelines on main and converts stable failures into KBEs and test-disable PRs.

Generated by CI Outer-Loop Failure Scanner · ● 85.3M · ◷