I have seen this in both CCNet/NAnt/MbUnit and TD.Net/MbUnit. My sightings are less frequent 1 in 6. They have been in frequent enough that I did not pursue the cause. Point being that my info is next to useless. ;-)
On 2/13/07, Andrew Stopford <[EMAIL PROTECTED]> wrote: > > Hmm ok thanks Simone. Has anyone else run into this while using > NAnt/CCNet/MbUnit ? > > It sounds like something is holding up the appdomain to prevent is being > dumped in the first run. I assume that all database and file code is being > closed off and disposed in the right way. Your not using any unmanaged/COM > code at all? > > Andy > > > On 2/13/07, Simone Chiaretta <[EMAIL PROTECTED]> wrote: > > > > The problem is that this is happening frequently... > > at least every 5-6 builds > > > > Simo > > > > On 2/14/07, Andrew Stopford < [EMAIL PROTECTED] > wrote: > > > > > > Hi, > > > > > > This may have been a one off and the force build has sorted it out. If > > > it keeps doing it then we can invesigate further. > > > > > > Andy > > > > > > On 2/13/07, Simone Chiaretta <[EMAIL PROTECTED] > wrote: > > > > > > > > Hi > > > > I'm using MbUnit inside our CCNET installation for subtext. > > > > Every now and then the build fails because of a problem with MbUnit > > > > > > > > it executes all the tests and the I've got this error: > > > > > > > > [exec] All Tests finished: 545 tests, 531 success, 0 failures, 14 > > > > ignored in 58.890625 seconds > > > > [exec] System.ApplicationException : Failed unloading domain ---> > > > > System.CannotUnloadAppDomainException: Error while unloading > > > > appdomain. (Exception from HRESULT: 0x80131015) > > > > [exec] at System.AppDomain.Unload(AppDomain domain) > > > > [exec] at MbUnit.Core.Remoting.SeparateTestDomain.Unload() > > > > [exec] --- End of inner exception stack trace --- > > > > [exec] at MbUnit.Core.Remoting.SeparateTestDomain.Unload() > > > > [exec] at MbUnit.Core.Remoting.TestDomainBase.Dispose() > > > > [exec] at MbUnit.Core.Graph.TestDomainDependencyGraph.Clear() > > > > [exec] at MbUnit.Core.Graph.TestDomainDependencyGraph.Dispose() > > > > [exec] at MbUnit.Core.Cons.MainClass.Main() > > > > > > > > If I force the build (I re run everything) it works again... > > > > > > > > Any idea of why that could happen? > > > > Here is the sample of the full build log: > > > > > > > > http://haacked.dyndns.org/ccnet/server/local/project/SubText-1.9/build/log20070212225554.xml/NAntOutputBuildReport.aspx#failure > > > > > > > > > > > > Thank you > > > > Simone > > > > > > > > -- > > > > Simone Chiaretta > > > > www.piyosailing.com/S > > > > Any sufficiently advanced technology is indistinguishable from magic > > > > > > > > "Life is short, play hard" > > > > > > > > > > > > > > -- > > Simone Chiaretta > > www.piyosailing.com/S > > Any sufficiently advanced technology is indistinguishable from magic > > "Life is short, play hard" > > > > > > -- Jay Flowers ---------------------------------------------------------------------- http://jayflowers.com --------------------------------------------------------------------- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
