Disable test explorer by removing the xUnit Visual Studio runner

[sharwell]

Works around major performance problems with Test Explorer in the current preview release (already fixed for an upcoming release but not yet available).

[Pilchie]

Tag @KevinH-MS I believe this explicitly contradicts the work to get Live Unit Testing working with Roslyn.sln 😦

[sharwell]

@Pilchie My goal is to bring this back ASAP, but until then we still have to get work done.

[KevinH-MS]

Unfortunate, but if the experience is significantly better without the adapters present, we can probably figure out some other (nonstandard) way for Live Unit Testing to work. Sam, can you elaborate on the pain so I can follow up with the test platform team? Is it just CPU cycles when opening solution/building, or are there other problems?

[sharwell]

@KevinH-MS Due to some issues in Test Explorer which are resolved but not yet shipped, we're experiencing high allocation rates which are resulting in pronounced GC-related usability problems. According to @davkean, these were measured in the range of ~1.5TiB of allocations.

[ManishJayaswal]

@sharwell - is there a bug tracking the TE window allocation issue that I can look at?

[tannergooding]

@sharwell, I thought it was 3.5TB and we reduced it by 1.5TB

[davkean]

It was merged in earlier today. https://devdiv.visualstudio.com/DevDiv/VS.in%20Agile%20Testing%20IDE/_workitems?id=454268&_a=edit From: Manish Jayaswal<mailto:notifications@github.com> Sent: Saturday, July 1, 2017 6:15 AM To: dotnet/roslyn<mailto:roslyn@noreply.github.com> Cc: David Kean<mailto:David.Kean@microsoft.com>; Mention<mailto:mention@noreply.github.com> Subject: Re: [dotnet/roslyn] Disable test explorer by removing the xUnit Visual Studio runner (#20569) @sharwell<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsharwell&data=02%7C01%7CDavid.Kean%40microsoft.com%7C6174768d335e4cf31e5108d4bff4c45b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636344505363677136&sdata=yp0EkdRietVhE0HO%2BYjGDJaq%2Bx1qbLqdZjL87IaVYX8%3D&reserved=0> - is there a bug tracking the TE window allocation issue that I can look at? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Froslyn%2Fpull%2F20569%23issuecomment-312363176&data=02%7C01%7CDavid.Kean%40microsoft.com%7C6174768d335e4cf31e5108d4bff4c45b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636344505363677136&sdata=XZphnJ3MxLY3ZgrxGiEF82pOfxEVScwBVSLhJnFZ%2BG0%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABDYIlG6g79W-DDc4xtIoumwnnTq8raFks5sJVdjgaJpZM4OKx_b&data=02%7C01%7CDavid.Kean%40microsoft.com%7C6174768d335e4cf31e5108d4bff4c45b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636344505363677136&sdata=UN2Kz09Ya%2FyjeN5%2B7TMY1VC02lkXZq2Om4d4Y4VvUcM%3D&reserved=0>.