-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Fix integration tests by adding skip for Codelens issue #77758
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
Fix integration tests by adding skip for Codelens issue #77758
Conversation
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.
Nice, thanks. Can we get this merged? I will then get rid of main-vs-deps.
EDIT: I haven't noticed integration tests were skipped...
All of these have been fixed long ago (or we suspect they've long been fixed.) Closes dotnet#35123
For reasons I'm unable to diagnose the codelens ServiceHub service is failing, possibly because it's missing a reference. I'm unable to sort out why, but it's not critical for integration tests so just ignore the failure.
bafbafc to
b44b0a3
Compare
b44b0a3 to
71785f3
Compare
71785f3 to
8c4f371
Compare
| && argumentException.Message.Contains("SnapshotPoint") | ||
| && argumentException.StackTrace.Contains("Microsoft.VisualStudio.Text.Editor.Implementation.WpfTextView.ValidateBufferPosition")) | ||
| if (exception.Message == "RemotePartyTerminated" && new System.Diagnostics.StackTrace().ToString().Contains("CodeLens") || | ||
| exception.Message == "Cannot access a disposed object.\r\nObject name: 'CodeLensHubClient'.") |
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.
do we really need the message to be that specific?
also, can we link this to a bug on the codelens people to fix whatever is going on?
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.
I'm going to file a tracking bug in a bit to clean up removing this once we're on a newer image since we expect things to resolve then.
We recently made some changes to upgrade to the 9.0 versions of various .NET packages; this had the effect of breaking our integration tests since the product wouldn't run at all on older versions of VS. I made a fix for that problem but integration tests were still failing. CodeLens is legitimately broken in this case right now, but this skips failing integration tests for that reason, since the tests otherwise pass fine.