Repository navigation
[ci-scan] Test failure: X509Certificate2CollectionRemoveRangeArray under crossgen2 #128444
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1427388
Build error leg or test failing: linux-x64 Release TestReadyToRun_Libraries - System.Security.Cryptography.Tests
Error Details
CollectionTests.X509Certificate2CollectionRemoveRangeArray fails under R2R/crossgen2 on linux-x64 and windows-x64. The test calls RemoveRange on an X509Certificate2Collection and expects 2 certificates to remain, but finds 0. This suggests a R2R compilation issue affecting the collection mutation logic.
[FAIL] System.Security.Cryptography.X509Certificates.Tests.CollectionTests.X509Certificate2CollectionRemoveRangeArray
Assert.Equal() Failure: Values differ
Expected: 2
Actual: 0
at System.Security.Cryptography.X509Certificates.Tests.CollectionTests.X509Certificate2CollectionRemoveRangeArray() in /_/src/libraries/System.Security.Cryptography/tests/X509Certificates/CollectionTests.cs:line 1037
at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result)
at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
Error Message
{
"ErrorMessage": ["X509Certificate2CollectionRemoveRangeArray", "Assert.Equal() Failure: Values differ"],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Affected legs:
- runtime-coreclr crossgen2 (def 124): linux-x64 Release TestReadyToRun_Libraries
- runtime-coreclr crossgen2 (def 124): windows-x64 Release TestReadyToRun_Libraries
- runtime-coreclr crossgen2 (def 124): osx-x64 Release TestReadyToRun_Libraries
First build it occurred: 1426059 (2026-05-19). Persistent across the entire scanned window (3+ consecutive builds); prior build 1424233 on 2026-05-18 succeeded.
Occurrences in window: 3+
Filed by ci-failure-scan, which scans dnceng-public outer-loop pipelines on main and converts stable failures into KBEs and test-disable PRs. Comment here or on the workflow file to suggest changes; ci-failure-scan-feedback reads in-scope feedback every 3 days and opens (or updates) a PR with prompt edits.
Note
🔒 Integrity filter blocked 2 items
The following items were blocked because they don't meet the GitHub integrity level.
- #125825
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #128392
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 | noneGenerated by CI Outer-Loop Failure Scanner · ● 61.6M · ◷
Activity
kotlarmilos commentedon May 21, 2026
Closing as not planned: the signature
["X509Certificate2CollectionRemoveRangeArray", "Assert.Equal() Failure: Values differ"]is too weak. The first element is a bare unqualified test method name that also appears in[PASS]and[SKIP]lines; the second is a generic xunit assertion stem that appears in thousands of unrelated Assert.Equal failures. Build Analysis would match this KBE against unrelated failures and produce "Known issue did not match with the provided build". Prompt fix pending in this branch: KBE check #6 now flags array-form signatures whose second element is a generic xunit assertion stem, and requires the uniqueExpected:/Actual:value lines. A fresh KBE with a tighter signature will be filed on the next scanner tick if the failure persists.ci-failure-scan: dedup stem fallback + reject weak array signatures