Home Dashboard Directory Help
Search

VSTestHost "hangs" make test runs impossible by marten_range


Status: 

Resolved
 as Not Reproducible Help for as Not Reproducible


0
0
Sign in
to vote
Type: Bug
ID: 339387
Opened: 4/22/2008 6:35:50 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

On certain machines (Virtual machines running ESX) we have the issue that VSTestHost never exits after the first test is completed.

Details
Sign in to post a comment.
Posted by Microsoft on 10/7/2008 at 8:25 PM
We are not able to repro. I am closing the bug for now
Posted by Microsoft on 5/22/2008 at 1:58 PM
Hi,

We will close this case with the hope that the workaround provided has fixed the issue. Please let us know if this is not the case.

Thanks

Visual Studio Team Test Product Team
Posted by marten_range on 5/20/2008 at 3:31 AM
Yes the workaround works. We have verified this on many machines. We are happy.


Thanks alot.
Posted by Microsoft on 5/19/2008 at 5:05 PM
Did the workaround work for you?

Let us know if we can help you further with this issue. If not, I will go ahead and close this bug.

Thanks,

Visual Studio Team Test Product Team
Posted by Microsoft on 5/9/2008 at 1:10 PM
Hi Mårten,

From the log, it looks like the issue is that the name of the computer/VM the Agent is running on is not uppercase. This is a known issue, and we are working on a fix for a future release.

As a workaround, you may try the following to change the computer name to uppercase:
1. Go to Start / Control Panel / System
2. Go to the Computer Name tab
3. Click on the Change button
4. Change the computer name to something different from what it is currently
5. Press OK until the dialogs disappear, and restart the computer
6. Repeat steps 1 to 3
7. Change the computer name back to what it was, making sure to type it in all uppercase letters
8. Press OK until the dialogs disappear, and restart the computer
9. To verify that the computer name is uppercase, you can open the Registry Editor (Start / Run, type regedit, and press OK), navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ComputerName", and verify that the ActiveComputerName and the ComputerName keys both have a value with the uppercase machine name.

Alternatively, although this is not recommended, you can change the registry values containing the machine name (mentioned in step 9) directly and then restart the computer, but make sure to back up the registry before you do this.

Thanks,

Visual Studio Team Test Product Team
Posted by marten_range on 5/9/2008 at 9:35 AM
Thanks for your reply.

I will do this but can't complete it until after the weekend as its of course working on my local machine.

The link you sent I do believe that's what I did when I generated the attachment VSTestHost.zip. In the log in the zip everything seems to proceed as it should until:

[V, 3716, 16, 2008/04/22 14:29:10.255] vstesthost.exe: AgentObject: WaitForTestState waiting for test 'TestMethod1' Completed, timeout is -1 current state is Uninitialized
[V, 3716, 17, 2008/04/22 14:29:10.255] vstesthost.exe: StateMachine(TestState): SetNextState Starting called
[V, 3716, 17, 2008/04/22 14:29:10.255] vstesthost.exe: StateMachine(TestState): calling state handler for Starting
[V, 3716, 17, 2008/04/22 14:29:10.270] vstesthost.exe: StateMachine(TestState): SetNextState Started called
[V, 3716, 17, 2008/04/22 14:29:10.270] vstesthost.exe: StateMachine(TestState): calling state handler for Started
[V, 3716, 17, 2008/04/22 14:29:10.270] vstesthost.exe: StateMachine(TestState): SetNextState Running called
[V, 3716, 17, 2008/04/22 14:29:10.286] vstesthost.exe: StateMachine(TestState): calling state handler for Running
[V, 3716, 18, 2008/04/22 14:29:10.301] vstesthost.exe: AgentExectution.CallAdapterRunMethod: calling into test adapter.
[E, 3716, 14, 2008/04/22 14:29:10.317] vstesthost.exe: AgentObject: TestMessagePump: Exception while calling IControllerCallback.AgentEvent: Microsoft.VisualStudio.TestTools.Exceptions.EqtException: There is no agent with the name 'Snejana' registered on the controller.
at Microsoft.VisualStudio.TestTools.Controller.AgentManager.GetAgentMachine(String agentName)
at Microsoft.VisualStudio.TestTools.Controller.ControllerObject.AgentEvent(String agentName, TestMessage message)


Snejana should be the name on the machine (its also the name of the developer but she should be logged in on a user name VSW\SNEJANA.GIOTINA).

What's interesting to me is that it seems the agent was allocated:
[V, 3716, 13, 2008/04/22 14:29:09.973] vstesthost.exe: Successfully verified connection for agent SNEJANA
[V, 3716, 8, 2008/04/22 14:29:09.973] vstesthost.exe: AgentManager: Agent 'SNEJANA' is now allocated

and some messaging seems to work.

Is it possible that its case sensitive (pure speculation on my part).

I would be very happy if we just could have a work around for this as it turns out we are experiencing this in other teams as well (same scenario, running VS2008 based on template with VS2008, the machine has been renamed and joined to domain).

Posted by Microsoft on 5/9/2008 at 9:21 AM
Hi,

After discussing this with others, we are unsure how the domain plays in a simple Unit test that doesn't do remote execution. On the other hand, we am sure something is causing it so we want to know if you can enable tracing for VSTestHost.exe per this blog http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=175052&SiteID=1 and review what is going on. Also, what happens if you create a project after joining the domain.

Thanks

Visual Studio Team Test Team
Posted by Microsoft on 4/22/2008 at 9:36 PM
Thanks for your feedback.

We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Sign in to post a workaround.