search

phuccaoca123 / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

Error when running tests with the debugger from TD.NET #47

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
When you run a test with TD.NET by selecting the option "Test With...
Debugger" an error occurs at the end of the execution. I've attached the 2
dialogs that appear. This happens after all the code of the
MbUnitTestRunner has been executed, and since I've seen the same error to
occur when some unhandled exception is thrown, I'm inclined to think that
it may be caused by a bug in Gallio, probably when disposing resources.

Original issue reported on code.google.com by julian.h...@gmail.com on 3 Sep 2007 at 2:02

Attachments:

GoogleCodeExporter commented 8 years ago 
Is this still a problem?

Original comment by jeff.br...@gmail.com on 19 Oct 2007 at 6:01

GoogleCodeExporter commented 8 years ago 
Yes, just tried it with the latest.

Original comment by julian.h...@gmail.com on 19 Oct 2007 at 6:25

GoogleCodeExporter commented 8 years ago 
Hmmm.  It works fine for me.  Let's chat later today and see if we can 
reproduce the
problem on my machine where I can see it.

I did notice that the TD.Net runner was a little sensitive to object references
sticking around.  When I removed the reference to the Gallio logger from the 
test
runner object, suddenly it was able to unload the Gallio assembly properly.  So 
now I
can make changes to Gallio and immediately go run the tests without having to 
shut
down the TD.Net helper program in the system tray.  It's a little strange.

Original comment by jeff.br...@gmail.com on 19 Oct 2007 at 6:37

GoogleCodeExporter commented 8 years ago 
Ahh!  I see it now.  I must have been blind earlier.  I'll check it out.

Original comment by jeff.br...@gmail.com on 19 Oct 2007 at 7:28

GoogleCodeExporter commented 8 years ago 
TD.Net doesn't seem to like us creating an isolated AppDomain during test 
execution.
 Or at least, it crashes inexplicably during debugging.  I didn't manage to trace it
back to any obvious cause.  The core dump produced by TD.Net is missing critical
information that could be used to pin-point the error using WinDbg and SOS.  
I'll see
about grabbing a crash-dump of ProcessInvoker.exe later.

So as a workaround, we use a local test domain instead of an isolated test 
domain
when running inside TD.Net.  That should work fine for the most part but it 
breaks
backwards-compatibility across versions of the MbUnit framework.

But at least debugging doesn't crash anymore for now...

Original comment by jeff.br...@gmail.com on 21 Oct 2007 at 10:12

GoogleCodeExporter commented 8 years ago 
Reverted back to using an isolated AppDomain after completing the IHost 
refactoring
and all seems well.

It could be that the old code was throwing an unhandled exception but in any 
case we
do not seem to be able to reproduce the problem any longer.

Original comment by jeff.br...@gmail.com on 16 Jan 2008 at 7:11