Skip to content
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

Use jsonSerializer2 for protocol version 3 #2630

Merged
merged 10 commits into from
Nov 16, 2020

Conversation

nohwnd
Copy link
Member

@nohwnd nohwnd commented Nov 12, 2020

Description

Updating the protocol to version 3 resulted in using serializer for v1, which sends two to three times more data. We cannot easily update how vstest.console behaves (e. g. the one shipped with net sdd 3.1.402), which will ask for protocol 3. So this PR will downgrade protocol 3 to 2. Any newer version would still be negotiable. Such as the protocol version 4 this PR introduces. Similarly protocol 3 is still using the old serializer, to keep compatibility in situations where we actually negotiate protocol 3. E.g. new console asking Test.SDK 16.7.1 for protocol version, where console would offer 4, but testhost would return 3. So 3 would be used with that specific version of SDK.

Related issue

Fix #2623

@nohwnd nohwnd merged commit a7046e3 into microsoft:master Nov 16, 2020
@@ -37,7 +37,7 @@ public class VsTestConsoleRequestSenderTests

private readonly int WaitTimeout = 2000;

private int protocolVersion = 3;
private int protocolVersion = 4;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

const for all version numbers?,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Microsoft.NET.Test.Sdk v16.7.0 and later are ~4x slower than v16.6.1
5 participants