Quarantine XmlKeyManagerTests.DeleteKeys

[wtgodbe]

Failing Test(s)

Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManagerTests.DeleteKeys

Error Message

Assert.Equal() Failure: Values differ
Expected: 4
Actual:   5

Stacktrace

Stack trace

at Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManagerTests.DeleteKeys() in /_/src/DataProtection/DataProtection/test/Microsoft.AspNetCore.DataProtection.Tests/KeyManagement/XmlKeyManagerTests.cs:line 976

Logs

Console log

[xUnit.net 00:00:03.54]     Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManagerTests.DeleteKeys [FAIL]
[xUnit.net 00:00:03.54]       Assert.Equal() Failure: Values differ
[xUnit.net 00:00:03.54]       Expected: 4
[xUnit.net 00:00:03.54]       Actual:   5
[xUnit.net 00:00:03.54]       Stack Trace:
[xUnit.net 00:00:03.54]         /_/src/DataProtection/DataProtection/test/Microsoft.AspNetCore.DataProtection.Tests/KeyManagement/XmlKeyManagerTests.cs(976,0): at Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManagerTests.DeleteKeys()
  Failed Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManagerTests.DeleteKeys [30 ms]
  Error Message:
   Assert.Equal() Failure: Values differ
Expected: 4
Actual:   5
  Stack Trace:
     at Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManagerTests.DeleteKeys() in /_/src/DataProtection/DataProtection/test/Microsoft.AspNetCore.DataProtection.Tests/KeyManagement/XmlKeyManagerTests.cs:line 976

Build

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1354831

[wtgodbe]

The test expects exactly 4 elements after a delete operation but finds 5. The DeleteKeys test creates keys, deletes some, and asserts on the remaining count. The extra element suggests either a timing issue with key creation/deletion or a race condition where an additional key element (possibly a revocation or metadata element) is being written to the XML repository between the delete and the count assertion. The test runs on net472 where threading behavior may differ from modern .NET. Unable to determine root cause with certainty.

[github-actions]

Triage Summary

Area: area-dataprotection — the failing test is XmlKeyManagerTests.DeleteKeys in src/DataProtection/DataProtection/test/.
Type: test-failure (already labeled) — CI test failure with a count assertion mismatch (Expected: 4, Actual: 5), indicating a flaky/non-deterministic test.

Potential Duplicates

• Quarantine XmlKeyManagerTests.DeleteKeys #66014 - "Quarantine XmlKeyManagerTests.DeleteKeys" (similarity: high — identical test, same assertion failure, same author; closed as not_planned earlier today)

Notes

This appears to be a re-filing of #66014, which was recently closed. The same flaky test (XmlKeyManagerTests.DeleteKeys) is failing again with the identical assertion error in a new CI build (buildId=1354831 vs the previous run). The fix (quarantining the test) may not have landed yet, or the test is continuing to fail before the quarantine PR merges.

Generated by Issue Triage Agent for dotnet/aspnetcore for issue #66029 · ◷

[DeagleGross]

was fixed #65989

[github-actions]

XmlKeyManagerTests.DeleteKeys has been passing 100% in the quarantined test pipeline for 30+ days. Unquarantine PR created.