-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skip Bundle_can_be_renamed() installer test #38014
Conversation
Tagging subscribers to this area: @vitek-karas, @swaroop-sridhar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Hello @swaroop-sridhar! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
@@ -22,7 +22,7 @@ public BundleRename(SharedTestState fixture) | |||
sharedTestState = fixture; | |||
} | |||
|
|||
[Theory] | |||
[Theory(Skip = "Fails in CI: https://github.com/dotnet/runtime/issues/35068")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use [ActiveIssue(...)] for such things in the library tests. I've not paid attention in the past to what's used in the installer tests. Are we able to use [ActiveIssue(...)] in such cases as well? If we haven't before, don't worry about it for this PR; in the future, it'd be nice to align across all the tests in the repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ActiveIssue should work fine as well in installer.
This test is randomly failing in the lab: dotnet#35068 Therefore skip this test until the underlying problem is resolved. Enabling the test is tracked by dotnet#38013 Fixes dotnet#35068.
caecad8
to
0f83ffb
Compare
This test is randomly failing in the lab: #35068
Therefore skip this test until the underlying problem is resolved.
Enabling the test is tracked by #38013
Fixes #35068.