[Mono-dev] [Ximian-mono-list] Mono unit test failures on windows...

[Andy Hume]

I don't know whether people are hitting those in the wild.  However, lots of
us are hitting:

** ERROR **: file mini.c: line 10315 (mono_get_lmf_addr): should not be
reached aborting...

https://bugzilla.novell.com/show_bug.cgi?id=414159
https://bugzilla.novell.com/show_bug.cgi?id=414310

I have to stand over my build system to close the assert dialog that pops up
when it runs the unit-tests on Mono.

Is there a solution to that one too?

TIA
Andy



Rodrigo Kumpera wrote:
> 
> Hi Jonathan,
> 
> Basically any test related to thread abort won't work on windows, this
> should account at least for:
> 
> appdomain-unload.exe
> finalizer-abort.exe
> 
> Half of the others look like bugs that require a smaller ammount of
> changes.
> 
> I'll add a more detailed explanation on bugzilla once I start looking at
> each bug.
> 
> Rodrigo
> 
> 
> On Mon, Nov 10, 2008 at 5:10 PM, Jonathan Chambers
> <joncham at gmail.com>wrote:
> 
>> Rodrigo,
>>      Can you specify (or try to specify) which ones require the big code
>> change? That way anyone interested can look at the other ones.
>>
>> Thanks,
>> Jonathan
>>
>> 2008/11/7 Rodrigo Kumpera <kumpera at gmail.com>
>>
>>> Hi Thomas,
>>>
>>> Thanks for taking time on this. I'll spend some time on this next week.
>>> What I can say is that at least half of those bugs won't be fixed for
>>> 2.2
>>> as they require
>>> a big code change.
>>>
>>> We came to a similar situation in the 2.0 time frame and decided to
>>> postpone it.
>>> The changes required to fix the whole thread interruption problem are
>>> quite complex
>>> and would better be done at the beginning of a release cycle and not
>>> close
>>> to its end.
>>>
>>> I hope we can get someone to work on this for the 2.4 as this is a
>>> significant source of
>>> instability for mono.
>>>
>>> Rodrigo
>>>
>>>
>>> On Fri, Nov 7, 2008 at 9:29 PM, Thomas Wiest <twiest at novell.com> wrote:
>>>
>>>> Hey Guys,
>>>>    As per Miguel's request, we've submitted bugs for the non-nunit unit
>>>> test failures on windows.
>>>>
>>>> Here they are:
>>>>
>>>> [test-runtime]
>>>> https://bugzilla.novell.com/show_bug.cgi?id=442812
>>>> https://bugzilla.novell.com/show_bug.cgi?id=442815
>>>> https://bugzilla.novell.com/show_bug.cgi?id=442816
>>>> https://bugzilla.novell.com/show_bug.cgi?id=442820
>>>> https://bugzilla.novell.com/show_bug.cgi?id=442990
>>>> https://bugzilla.novell.com/show_bug.cgi?id=442994
>>>> https://bugzilla.novell.com/show_bug.cgi?id=442997
>>>> https://bugzilla.novell.com/show_bug.cgi?id=443051
>>>> https://bugzilla.novell.com/show_bug.cgi?id=443056
>>>>
>>>> [test-cas]
>>>> https://bugzilla.novell.com/show_bug.cgi?id=443003
>>>>
>>>> [test-compiler-2.0]
>>>> https://bugzilla.novell.com/show_bug.cgi?id=443024
>>>>
>>>>
>>>> We will be e-mail out the failures for the nunit based tests.
>>>>
>>>>
>>>> Thomas
>>>>
>>>>
>>>> _______________________________________________
>>>> Ximian-mono-list mailing list
>>>> Ximian-mono-list at lists.ximian.com
>>>> http://lists.ximian.com/mailman/listinfo/ximian-mono-list
>>>>
>>>
>>>
>>> _______________________________________________
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>
>>>
>>
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> 

-- 
View this message in context: http://www.nabble.com/Mono-unit-test-failures-on-windows...-tp20390836p20436232.html
Sent from the Mono - Dev mailing list archive at Nabble.com.