[ci-scan] Mark SwiftErrorHandling as InterpreterIncompatible

[github-actions]

Caution

Security scanning requires review for CI Outer-Loop Failure Scanner

Details

The threat detection results could not be parsed. The workflow output should be reviewed before merging.

Review the workflow run logs for details.

Linked KBE: #127897

Marks SwiftErrorHandling test as <InterpreterIncompatible>true</InterpreterIncompatible> because the CoreCLR interpreter does not implement the Swift error-return calling convention.

Verification

1. Same test (or test family)? Yes — SwiftErrorHandling.TestSwiftErrorThrown is the failing test in KBE [ci-scan] Known Build Error: SwiftErrorHandling.TestSwiftErrorThrown fails in runtime-interpreter #127897.
2. Same failure signature? Yes — Xunit.Sdk.TrueException: A Swift error was expected to be thrown.
3. OS in scope? Yes — osx (arm64, x64) as reported in KBE.
4. Architecture in scope? Yes — arm64 and x64.

Failing legs

• runtime-interpreter (def 316): osx-arm64 Checked, osx-x64 Checked

The InterpreterIncompatible flag skips the test only under interpreter mode, matching the observed failure scope exactly.

Note

🔒 Integrity filter blocked 3 items

The following items were blocked because they don't meet the GitHub integrity level.

• #85747 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #114222 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #125825 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

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