Skip to content

Conversation

@jasonmalinowski
Copy link
Member

@jasonmalinowski jasonmalinowski commented Mar 22, 2025

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.

@ghost ghost added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Mar 22, 2025
Copy link
Member

@jjonescz jjonescz left a 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...

@dotnet dotnet deleted a comment from azure-pipelines bot Mar 24, 2025
@dotnet dotnet deleted a comment from azure-pipelines bot Mar 24, 2025
@dotnet dotnet deleted a comment from jaredpar Mar 24, 2025
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.
@jasonmalinowski jasonmalinowski marked this pull request as ready for review March 24, 2025 19:20
@jasonmalinowski jasonmalinowski requested review from a team as code owners March 24, 2025 19:20
@jasonmalinowski jasonmalinowski changed the title Fix integration tests Fix integration tests by adding skip for Codelens issue Mar 24, 2025
@jasonmalinowski jasonmalinowski self-assigned this Mar 24, 2025
&& 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'.")
Copy link
Member

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?

Copy link
Member Author

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.

@jasonmalinowski jasonmalinowski merged commit a7fcc1f into dotnet:main-vs-deps Mar 24, 2025
25 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Mar 24, 2025
@jasonmalinowski jasonmalinowski deleted the fix-integration-tests branch March 24, 2025 23:54
@jjonescz jjonescz modified the milestones: Next, 17.14 P3 Apr 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants