chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
0 votes
In addition to a scenario that I described yesterday (TypeMock 6.x) causes build on build machine hang, a combination of TypeMock and TestDriven on a local development machine also occasionally hung after executing all tests. The only way to go forward was to kill ProcessInvocation.exe.

Interestingly, the problem went away when I installed latest beta of TestDriven.NET (3.0 beta 2). Still, since there's been several reports about Isolator 6.0 behavior in combination with other products, I believe the issue has something to do with Isolator (I've been successfully using TestDriven.NET 2.24 for a long time).
asked by vagif (19.4k points)

12 Answers

0 votes
Hi Vagif,

Does it reproduces on any project or just specific one? What version ofther issue Test-Driven are you using? We'll investigate it, it's likely related to the other issue you reported.

Regards,
Elisha,
Typemock Support
answered by Elisha (12k points)
0 votes
Hi Elisha,

IMHO it is not related to one specific project, because this happenned to several developers working on different things. All machines where this problem occurred had TestDriven 2.24 and TypeMock 6.0 or 6.01 installed. Upgrading to TestDriven 3.0 beta 2 fixed the problem.
answered by vagif (19.4k points)
0 votes
Hi,

We've fixed this bug. I'll send you patch soon.

This fix will be part of the new version we'll release soon.

Regards,
Elisha,
Typemock Support
answered by Elisha (12k points)
0 votes
Hi Elisha,

Thank you for the fix. We first tried it on development machines, and it seems to work. Tomorrow we are going to install it on a build server. I'll let you know.
answered by vagif (19.4k points)
0 votes
Just to confirm that I also have the same problem.

I'll download test driven 3.0 and see whether the problem is still there
answered by nsoonhui (59.1k points)
edited by Bar
0 votes
We installed a patch on a several machines and it _mostly_ works. Unfortunately not always.

1. Works on development machine that has TestDriven.NET. I switched back to TD 2.24 that used to hung with Isolator 6.0, and now it works.

2. On our build server sometimes it hangs while running unit tests with code coverage generation. Not always, and not after the first test project. Occasionally it executes unit tests on several projects and then hangs. And it is always the same project where it hangs.
answered by vagif (19.4k points)
0 votes
Unfortunately we had to rollback to Isolator 5.4.5 on our build server. Same symptoms: suddenly whole build just hangs. After unit tests are executed and before coverage report is generated.

On development machines patch worked.
answered by vagif (19.4k points)
0 votes
Hi,

Thanks for letting us know. We're putting all our effort on fixing this bug. It does seem the previous patch solves on part of the problem. We're testing at the moment a new patch and I hope it'll be ready soon.

Regards,
Elisha,
Typemock Support
answered by Elisha (12k points)
0 votes
Elisha,
Could this bug be related to this one?
https://www.typemock.com/community/viewtopic.php?t=1709

I have not had time to put together a project to send over for testing.

Thanks.
answered by teom (2.3k points)
0 votes
I think the latest version 6.0.2.0 solves the problem, thanks.
answered by nsoonhui (59.1k points)
edited by Bar
...