Hi,
I am running test framework 2010.3.1109. I have the same issue when I tried version 2011.1.609. I am using TeamCity and nunit to run the automation tests.
We typically run a set of 3 to 7 tests (one story) and then shutdown the browser for a clean start on the next story's tests.
Chrome runs fine. However both IE 8 and FireFox 3.6 exhibit the following problems:
Whenever we shut down the browser by calling ShutDown() we get this exception: System.Threading.ThreadAbortException: Thread was being aborted The tests continue to run. However eventually we get the following exception: System.IO.IOException: All pipe instances are busy At this point the browsers open but do not navigate to the starting URL.
My guess is that the aborted threads are leaving a pipe instance open, and that eventually the server runs out of pipes.
I can handle the problem by putting in a sleep after each shutdown. However this adds a lot of time to our tests. In some cases I need a sleep as long as 30 seconds. At least I think this will handle the problem. I am trying the 30 second sleep now. Also the ThreadAbortExceptions clutter the logs.
Are there any better solutions?
Rob
I am running test framework 2010.3.1109. I have the same issue when I tried version 2011.1.609. I am using TeamCity and nunit to run the automation tests.
We typically run a set of 3 to 7 tests (one story) and then shutdown the browser for a clean start on the next story's tests.
Chrome runs fine. However both IE 8 and FireFox 3.6 exhibit the following problems:
Whenever we shut down the browser by calling ShutDown() we get this exception: System.Threading.ThreadAbortException: Thread was being aborted The tests continue to run. However eventually we get the following exception: System.IO.IOException: All pipe instances are busy At this point the browsers open but do not navigate to the starting URL.
My guess is that the aborted threads are leaving a pipe instance open, and that eventually the server runs out of pipes.
I can handle the problem by putting in a sleep after each shutdown. However this adds a lot of time to our tests. In some cases I need a sleep as long as 30 seconds. At least I think this will handle the problem. I am trying the 30 second sleep now. Also the ThreadAbortExceptions clutter the logs.
Are there any better solutions?
Rob