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

2008-11-11 Thread Charlie Poole
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy Hume Sent: Tuesday, November 11, 2008 1:41 AM To: mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] [Ximian-mono-list] Mono unit test failures on windows... I don't know whether people are hitting those in the wild

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

2008-11-11 Thread 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

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

2008-11-11 Thread Thomas Wiest
Bill Holmes wrote: Hi, I believe that r118412 fixes https://bugzilla.novell.com/show_bug.cgi?id=443056 at least. Ok, I closed the bug. Thanks! Thomas ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com

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

2008-11-10 Thread Jonathan Chambers
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 [EMAIL PROTECTED] Hi Thomas, Thanks for taking time on this. I'll spend some time on this next week.

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

2008-11-10 Thread Bill Holmes
Hi, I believe that r118412 fixes https://bugzilla.novell.com/show_bug.cgi?id=443056 at least. -bill ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list

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

2008-11-07 Thread Rodrigo Kumpera
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