[Mono-dev] Test suite failures (Mono 2.10.2)
David Schmitt
david at dasz.at
Fri Jun 24 16:35:07 EDT 2011
On 24/06/11 21:14, Harry Wilkinson wrote:
> Okay, so I guess this answers 2 of the questions - the test failures are
> expected, and I'm not doing anything wrong. Please correct me if you
> think otherwise.
>
> I would still really like to know: how is Mono packaged if the test
> suite fails?
>
> This is important to me because I would like to build my own package so
> I don't have to compile Mono every time I deploy a Mono app. Is there a
> straightforward way to ignore the tests?
don't run make check and/or do not use --enable-nunit-tests ?
Debian (courtsy of meeby and friends) is currently working on getting
2.10 ready for testing. Current packages are in experimental. Take a
look at the source at:
http://anonscm.debian.org/gitweb/?p=pkg-mono/packages/mono.git
Best Regards, David
>
> Thanks.
>
> Harry
>
> Date: Fri, 24 Jun 2011 15:12:12 -0300
> From: Rodrigo Kumpera <kumpera at gmail.com <mailto:kumpera at gmail.com>>
> Subject: Re: [Mono-dev] Test suite failures (Mono 2.10.2)
> To: Kocsis L?szl? <kocsis1977 at gmail.com <mailto:kocsis1977 at gmail.com>>
> Cc: mono-devel-list at lists.ximian.com
> <mailto:mono-devel-list at lists.ximian.com>
> Message-ID: <BANLkTinXuJQsmHyu8JY48JxeTZCxZfJ1wQ at mail.gmail.com
> <mailto:BANLkTinXuJQsmHyu8JY48JxeTZCxZfJ1wQ at mail.gmail.com>>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I think you misundestood my email. It's the opposite, right now we, at
> Xamarin,
> can't really afford the time to bring the mono CI infrastructure back so
> someone
> from the community needs to step up and do it.
>
>
>
> On Fri, Jun 24, 2011 at 3:07 PM, Kocsis L?szl? <kocsis1977 at gmail.com
> <mailto:kocsis1977 at gmail.com>> wrote:
>
>> Hi Rodrigo,
>>
>> Good news the guys at Xamarin are working hard on "getting the build
>> infrastructure back". Would you please give us an estimate about when
>> will it be up and running again?
>>
>> I would like to work on bugs in the Windows version of mono, but I
>> could not even compile it. I hope the automatic build and test system
>> will solve such problems and mono will compile and pass all tests at
>> least on every major platform. Or am I naive and this cannot be
>> expected?
>>
>> Best,
>>
>> Laszlo
>>
>>
>> 2011/6/24, Rodrigo Kumpera <kumpera at gmail.com <mailto:kumpera at gmail.com>>:
>> > It's hard to do such a thing when you factor in that mono supports many
>> > dozens of targets and configurations and
>> > that sometimes those breaks were caused my maintainers - I have my share
>> of
>> > faults.
>> >
>> > Thing is, right now the team at Xamarin has tons of stuff on its hand so
>> > getting the build infrastructure back on
>> > track, which helps us a lot, won't happen without community help.
>> >
>> > A good first step would be to get CI back working at least on linux. S,
>> if
>> > someone wants to rebuild the continuous
>> > integration farm over linode (or other VPS) please speak up.
>> >
>> >
>> > On Thu, Jun 23, 2011 at 4:05 PM, Steve Bjorg <steveb at mindtouch.com
> <mailto:steveb at mindtouch.com>>
>> wrote:
>> >
>> >> Here's a thought: only accept code changes that pass all tests? Just
>> >> saying...
>> >>
>> >> - Steve
>> >>
>> >> --------------
>> >> Steve G. Bjorg
>> >> http://mindtouch.com <http://mindtouch.com/>
>> >> http://twitter.com/bjorg
>> >>
>> >> On Jun 23, 2011, at 11:43 AM, Zoltan Varga wrote:
>> >>
>> >> Hi,
>> >>
>> >> Our test suite contains 1000s of tests, written by dozens of people,
>> its
>> >> a bit hard to keep them all passing.
>> >>
>> >> Zoltan
>> >>
>> >> On Thu, Jun 23, 2011 at 7:44 PM, Harry Wilkinson
>> >> <hwilkinson at mdsol.com <mailto:hwilkinson at mdsol.com>>wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> I'm encountering some test failures with the Mono 2.10.2 source
> tarball
>> >>> distributed at http://ftp.novell.com/pub/mono/sources/mono/
>> >>>
>> >>> Basically I'm trying to package it for deployment on Ubuntu 10.04.2
>> >>> servers in a cloud configuration. So far I've been building from
>> source
>> >>> and
>> >>> encountered no significant problems other than the long build time.
>> I'd
>> >>> like to be able to reduce that by building it once and deploying a
>> >>> compiled
>> >>> package. So I'm using dpkg-buildpackage.
>> >>>
>> >>> However, now that I'm packaging rather than just building and
>> installing,
>> >>> it seems that the test suite is run and there are some test failures.
>> >>> The
>> >>> first and most obvious one is that it appears that a file is missing
>> from
>> >>> the source tarball:
>> >>>
>> >>>
>> >>>
>>
> mcs/class/corlib/Test/System.Runtime.Serialization.Formatters.Binary/VersionTolerantSerialization/VersionTolerantSerializationTestLib/6.0/Address.cs
>> >>>
>> >>> The file is there in the Git repo under the 2.10.2 tag, but it's
> not in
>> >>> the tarball. Unfortunately it's referenced in the associated Makefile
>> >>> (mcs/class/corlib/Makefile). The same applies to 2.10.1, so I'm
>> guessing
>> >>> the file is omitted from whatever process builds the tarballs.
>> >>>
>> >>> I switched to compiling from the source taken from Git, checkout out
>> the
>> >>> 2.10.2 tag, and I get a different error (which is also what I get with
>> >>> the
>> >>> tarball version if I just hack the makefile):
>> >>>
>> >>> make[8]: Entering directory
>> >>> `/home/hwilkinson/mono/mcs/class/System.Web.DynamicData'
>> >>> MCS [net_2_0] System.Web.DynamicData_test_net_2_0.dll
>> >>>
>>
> Test/../../System.Web/Test/mainsoft/NunitWeb/NunitWeb/MyTemplateControls.cs(43,19):
>> >>> error CS0507:
>> >>> `MyTemplateControls.TestTemplateControl.CreateChildControls()': cannot
>> >>> change access modifiers when overriding `protected' inherited member
>> >>> `System.Web.UI.Control.CreateChildControls()'
>> >>> /home/hwilkinson/mono/mcs/class/lib/net_2_0/System.Web.dll
> (Location of
>> >>> the symbol related to previous error)
>> >>> Compilation failed: 1 error(s), 0 warnings
>> >>> make[8]: *** [System.Web.DynamicData_test_net_2_0.dll] Error 1
>> >>>
>> >>> It looks like this could well be an incorrect preprocessor definition
>> >>> 'SYSTEM_WEB_EXTENSIONS' (not sure whether it should be defined or not)
>> >>> in
>> >>>
>>
> mcs/class/System.Web/Test/mainsoft/NunitWeb/NunitWeb/MyTemplateControls.cs.
>> >>>
>> >>> Is this expected? I had sort of assumed that a released version would
>> >>> have a passing test suite. Am I doing something wrong?
>> >>>
>> >>> Any advice (well, almost) would be gratefully received.
>> >>>
>> >>> Thanks.
>> >>>
>> >>> Harry Wilkinson
>> >>>
>> >>> _______________________________________________
>> >>> Mono-devel-list mailing list
>> >>> Mono-devel-list at lists.ximian.com
> <mailto: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
> <mailto: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
> <mailto: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
More information about the Mono-devel-list
mailing list