You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While running runtime-libraries-mono outerloop tests we noticed that test cases marked with the OuterLoop attribute, which also have attributes like ActiveIssue or SkipOnPlatform, are still being executed and causing failures in the pipeline.
For example, the following test will still run on the browser platform:
[OuterLoop]
[SkipOnPlatform(TestPlatforms.Browser, "Not supported on browser")]
This command should work correctly by excluding tests that shouldn't run on specific platforms.
Side Note: If we include the TestPlatforms parameter with the OuterLoop attribute, it respects the platform exclusion, and the tests are skipped as expected. For example:
[OuterLoop("Resource-intensive due to parallel processing", ~TestPlatforms.Browser)]
[SkipOnPlatform(TestPlatforms.Browser, "Not supported on browser")]
The text was updated successfully, but these errors were encountered:
While running runtime-libraries-mono outerloop tests we noticed that test cases marked with the
OuterLoop
attribute, which also have attributes likeActiveIssue
orSkipOnPlatform
, are still being executed and causing failures in the pipeline.For example, the following test will still run on the browser platform:
The command passed to Xharness contains:
-trait category=OuterLoop -notrait category=IgnoreForCI -notrait category=failing
This command should work correctly by excluding tests that shouldn't run on specific platforms.
Side Note: If we include the TestPlatforms parameter with the OuterLoop attribute, it respects the platform exclusion, and the tests are skipped as expected. For example:
The text was updated successfully, but these errors were encountered: