disable tests unstable on Windows 11

[wfurt]

contributes to #58927

cc: @ViktorHofer

[ghost]

Tagging subscribers to this area: @dotnet/ncl, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

---

contributes to #58927

cc: @ViktorHofer

Author:	wfurt
Assignees:	wfurt
Labels:	area-System.Net.Security
Milestone:	-

[antonfirsov]

Why ConditionalTheory if there are no actual conditions passed to it? Is it needed for SkipTestException to work?

[ViktorHofer]

That's necessary for SkipTestException to work. The condition isn't statically defined but dynamically via throwing an Exception.

[wfurt]

BTW this is our own extension and that is also why Microsoft.DotNet.XUnitExtensions is needed @antonfirsov

[karelz]

Unrelated test failure in System.ComponentModel.EventBasedAsync.Tests:

    System.ComponentModel.EventBasedAsync.Tests.BackgroundWorkerTests.TestCancelAsync [FAIL]
      Cancellation in Main thread
      Expected: True
      Actual:   False
      Stack Trace:
        /_/src/libraries/System.ComponentModel.EventBasedAsync/tests/BackgroundWorkerTests.cs(126,0): at System.ComponentModel.EventBasedAsync.Tests.BackgroundWorkerTests.TestCancelAsync()
        /_/src/mono/System.Private.CoreLib/src/System/Reflection/RuntimeMethodInfo.cs(370,0): at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
    System.ComponentModel.EventBasedAsync.Tests.BackgroundWorkerTests.TestFinalization [SKIP]
      Condition(s) not met: "IsPreciseGcSupported"

Re-running failed leg

[ViktorHofer]

@karelz thanks for pointing out the unrelated test failure. What would help even more is if you could file an issue for it (in this case one doesn't exist yet) so that this information isn't lost in the nirvana of merged PRs.

[karelz]

@ViktorHofer I am hesitant to file one off test failures as they are super-noisy in Networking for example (we close them right away) -- IMO people searching for it will find the PR and if they see it 2nd time, they can create issue ... optimizing for process ;)

[ViktorHofer]

The official guidance has been to open issues for every unrelated test failure immediately so that area owners can look into the failures and triage them. In some cases such failures might just be noise (still our tests needs to handle that) but in other cases they might surface an underlying product issue.

[wfurt]

/backport to release/6.0

[wfurt]

/backport to release/6.0

[github-actions]

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1670024962