在.Net 4.6升级后，使用Visual Studio Test步骤构建错误 - Executor进程退出; net.pipe上没有端点监听 [英] VSO CI Build Error with Visual Studio Test step after .Net 4.6 upgrade - Executor process exited; There was no endpoint listening at net.pipe

问题描述

我刚刚升级了我的解决方案中的所有项目，指向.Net 4.6（有一个Web应用程序，一些类库，一个数据库项目等）。我在Visual Studio Online中设置了CI构建（使用新的构建系统，而不是XAML），它在升级之前成功构建了
。此构建定义运行Debug，Staging和Production构建，构建定义包含两个步骤：

I just upgraded all of the projects in my solution to point to .Net 4.6 (There is a web app, some class libraries, a database project, etc.). I have a CI build set up in Visual Studio Online (using the new build system, not XAML) which was building successfully prior to the upgrade. This build definition runs Debug, Staging, and Production builds and the build definition is comprised of two steps:

• Visual Studio Build
• Visual Studio测试

在此框架升级之前，一切都很好。我在本地升级并构建了一切，这一切都很有效。我可以运行测试并全面获得绿色。现在，当我在其中检查我的代码时，启动了CI构建，并且在"Visual Studio测试"中获得了
跟随错误/ s step（取自日志）：

Prior to this framework upgrade, everything was building fine. I upgraded and built everything locally and it all worked great too. I could run the tests and got green across the board. Now, when I checked my code in it kicked off the CI build, and I got the following error/s on the "Visual Studio Test" step (taken from the logs):

2015-09-18T19:08:02.1212067Z Microsoft (R) Test Execution Command Line Tool Version 14.0.23107.0
2015-09-18T19:08:02.1489666Z Copyright (c) Microsoft Corporation.  All rights reserved.
2015-09-18T19:08:02.8906952Z Starting test execution, please wait...
2015-09-18T19:08:03.3713251Z Warning: Using Isolation mode to run tests as required by effective Platform:X86 and .Net Framework:Framework35 settings for test run. Use the /inIsolation parameter to suppress this warning.
2015-09-18T19:08:07.4457804Z ##[error]Error: Executor process exited.
2015-09-18T19:08:07.4457804Z ##[error]
2015-09-18T19:08:07.4557251Z ##[error]Error: There was no endpoint listening at net.pipe:[...redacted...] that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
2015-09-18T19:08:07.4557251Z ##[error]
2015-09-18T19:08:07.7730938Z ##[error]VSTest Test Run failed with exit code: 1
2015-09-18T19:08:07.8043435Z ##[warning]No results found to publish.

Visual Studio Build传递对于所有三种配置，测试步骤仅对Debug失败，因为它无法找到其他两种配置的任何测试。另外，我的构建运行的是Azure VM，我站起来充当构建服务器，
，当我使用Hosted构建控制器运行CI构建时，Test步骤通过，因为它无法找到任何测试执行，但是关于使用'隔离模式运行测试...'的警告仍打印在日志中。

The Visual Studio Build passes for all three configurations, and the Test step only fails for Debug because it cannot find any tests for the other two configurations. Additionally, my builds are running off of an Azure VM that I stood up to act as a build server, and when I run the CI build using the Hosted build controller the Test step passes, because it cannot find any tests to execute, but the warning about using 'Isolation mode to run tests...' is still printed out in the log.

这是一个已知问题吗？有没有其他人在4.6升级后或在VSO的另一个上下文中遇到过这个？

Is this a known issue? Has anyone else encountered this after a 4.6 upgrade or in another context in VSO?

此外，.Net框架和所有内容都安装在构建服务器上，我能够打开该计算机上的Visual Studio并成功运行所有测试。

Also, .Net framework and everything are installed on the build server, and I am able to open up Visual Studio on that machine and run all of the tests successfully.

推荐答案

我发现暂时的解决方法现在有效。我修改了Visual Studio Test构建步骤的设置，如下所示：

I found a workaround for the time being that works for now. I modified the settings for the Visual Studio Test build step as follows:

On  Build  步骤设置的标签，展开"高级"按钮部分，并将VSTest版本更改为"Visual Studio 2013"​​。

On the Build tab of the step settings, expand the "Advanced" section, and change the VSTest version to "Visual Studio 2013".

这就是我所需要的一切。我尝试了这个，因为当我切换到托管构建控制器时，我的构建工作正常，这是日志中两者之间的差异之一。这是我改变的唯一一件事，它起作用了。我不知道为什么
Visual Studio 2015 VSTest版本不起作用，但如果我发现任何内容，我会更多地查看它并添加到此...

That's all it took for me. I tried this because my build was working when I switched to the Hosted build controller, and this was one of the differences between the two in the logs. This is the only thing that I changed, and it worked. I have no idea WHY the Visual Studio 2015 VSTest version doesn't work, but will look into it more and add to this if I find anything...

这篇关于在.Net 4.6升级后，使用Visual Studio Test步骤构建错误 - Executor进程退出; net.pipe上没有端点监听的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！