Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[David Schmitt]

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 mailto:kump...@gmail.com>>
> Subject: Re: [Mono-dev] Test suite failures (Mono 2.10.2)
> To: Kocsis L?szl? mailto:kocsis1...@gmail.com>>
> Cc: mono-devel-list@lists.ximian.com
> <mailto:mono-devel-list@lists.ximian.com>
> Message-ID:  <mailto:banlktinxujqsmhyu8jy48jxetzcxzfj...@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?  <mailto:kocsis1...@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 mailto:kump...@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  <mailto:ste...@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
>>  >> mailto:hwilkin...@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
>>  &

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Harry Wilkinson]

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?

Thanks.

Harry

Date: Fri, 24 Jun 2011 15:12:12 -0300
From: Rodrigo Kumpera 
Subject: Re: [Mono-dev] Test suite failures (Mono 2.10.2)
To: Kocsis L?szl? 
Cc: mono-devel-list@lists.ximian.com
Message-ID: 
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?  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 :
> > 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 
> wrote:
> >
> >> Here's a thought: only accept code changes that pass all tests?  Just
> >> saying...
> >>
> >> - Steve
> >>
> >> --
> >> Steve G. Bjorg
> >> 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
> >> 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

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Kocsis László]

Ooops. I thought you need community help, but you at Xamarin are also
working on it. How do you imagine a build system installed by the
community? What does it exactly mean that "someone from the community
needs to step up and do it"?

For example, I could hack together an automatic build system on
Windows (XP, Vista, 7), but this won't be of much help because I would
simply run into compilation problems just as I did some days ago.
Maybe I am not right but I think mono would need some serious
*central* quality management in order to stop contributors breaking
the build or ruining unit tests. Maybe this can be done in a
*distributed* way, but I don't have a clue how. I think the code sent
in by community members should be checked (compiled and tested) *at
Xamarin* before it becomes part of the official release.

I would be happy to help making the Windows release stable. Please
tell me what can I do. I really would like to help.

Laszlo




2011/6/24, Rodrigo Kumpera :
> 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ó  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 :
>> > 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 
>> wrote:
>> >
>> >> Here's a thought: only accept code changes that pass all tests?  Just
>> >> saying...
>> >>
>> >> - Steve
>> >>
>> >> --
>> >> Steve G. Bjorg
>> >> 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
>> >> 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.CreateC

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[David Schmitt]

On 24/06/11 19:02, Rodrigo Kumpera wrote:
> 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.

I know how annoying it is to wait for unit tests to run before 
comitting. It's much better to send that off to some server and code on :)

> 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.

Non-functional unit tests are *the* major frustration for me when trying 
to work on mono. Since I'm building a product which also should run on 
mono, I do have a big interest in getting mono development back on 
track, and improve the release quality (e.g. by avoiding regressions 
through a working test infrastructure).

I've got extensive experience adminning Debian, a few years on RedHat, 
and I'm responsible for the CC.NET server at my company. So, please just 
tell me how I can help!


Best Regards, David
>
>
> On Thu, Jun 23, 2011 at 4:05 PM, Steve Bjorg  > wrote:
>
> Here's a thought: only accept code changes that pass all tests?
>   Just saying...
>
> - Steve
>
> --
> Steve G. Bjorg
> 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
>> mailto:hwilkin...@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
>>   

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Rodrigo Kumpera]

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ó  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 :
> > 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 
> wrote:
> >
> >> Here's a thought: only accept code changes that pass all tests?  Just
> >> saying...
> >>
> >> - Steve
> >>
> >> --
> >> Steve G. Bjorg
> >> 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
> >> 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@lists.ximian.com
> >>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> >>>
> >>>
> >> __

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Kocsis László]

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 :
> 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  wrote:
>
>> Here's a thought: only accept code changes that pass all tests?  Just
>> saying...
>>
>> - Steve
>>
>> --
>> Steve G. Bjorg
>> 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
>> 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@lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>
>>>
>> ___
>> Mono-devel-list mailing list
>> Mono-devel-list@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
>>
>> ___
>> Mono-devel-list mailing list
>> Mono-devel-list@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Rodrigo Kumpera]

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  wrote:

> Here's a thought: only accept code changes that pass all tests?  Just
> saying...
>
> - Steve
>
> --
> Steve G. Bjorg
> 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 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@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
>
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Harry Wilkinson]

I don't mean to cast aspersions on the maintenance of the tests (although I
do think it would be unusual if a product was released with failures in its
own automated test suite).  I don't feel entitled to complain too much, but
I'd like to understand the situation.

I just want to find answers to these questions:

   1. Is this expected
  - in general? (It sounds like yes, please somebody correct this if
  they think otherwise)
  - for a released version? (Sounds like yes again)
  - for 2.10.2?
   2. Does it look like I'm doing something wrong?
   3. How is Mono packaged if the test suite fails?

Thanks again.

Harry

On 23 June 2011 20:05, Steve Bjorg  wrote:

> Here's a thought: only accept code changes that pass all tests?  Just
> saying...
>
>- Steve
>
> --
> Steve G. Bjorg
> 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 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@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Robert Jordan]

On 23.06.2011 21:05, Steve Bjorg wrote:
> Here's a thought: only accept code changes that pass all tests?  Just 
> saying...

Here is a second thought: the build servers are down, QA is gone,
RE is gone. Just saying...

The errors below are solely caused by lack of infrastructure.

>
> - Steve
>
> --
> Steve G. Bjorg
> 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  
>> 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@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
>> ___
>> Mono-devel-list mailing list
>> Mono-devel-list@lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
>
>
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list


___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Zoltan Varga]

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 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@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test suite failures (Mono 2.10.2)

[Steve Bjorg]

Here's a thought: only accept code changes that pass all tests?  Just saying...

- Steve

--
Steve G. Bjorg
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  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@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> 
> ___
> Mono-devel-list mailing list
> Mono-devel-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] Test suite failures (Mono 2.10.2)

[Harry Wilkinson]

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@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test Suite Failures, Revision 2

[Atsushi Eno]

Thanks! It's looking good and working fine, so please go ahead and 
commit the change.

Atsushi Eno

On 2010/04/06 6:35, Gonzalo Paniagua Javier wrote:
> On Mon, 2010-04-05 at 14:28 +0900, Atsushi Eno wrote:
>
>>> -- test-System_ServiceModel --
>>> 6 sporadic timeouts
>>> started in r154243 (Gonzalo)
>>> http://build.mono-project.com/GetFile.aspx?id=2257888
>>>
>> Gonzalo, tell me if you got some fixes. I'll stick to r154237 so far
>> (after updating my repo it was blocking nunit test run there, so I have
>> reverted to older version).
>>  
> These is fixed now.
>
> I'm attaching a patch for HttpRequestChannel.cs that avoids creating the
> ManualResetEvent when nobody needs it. Ok to commit?
>
> -Gonzalo
>
>

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test Suite Failures, Revision 2

[Gonzalo Paniagua Javier]

On Mon, 2010-04-05 at 14:28 +0900, Atsushi Eno wrote:
> > -- test-System_ServiceModel --
> > 6 sporadic timeouts
> > started in r154243 (Gonzalo)
> > http://build.mono-project.com/GetFile.aspx?id=2257888
> 
> Gonzalo, tell me if you got some fixes. I'll stick to r154237 so far 
> (after updating my repo it was blocking nunit test run there, so I have 
> reverted to older version).

These is fixed now.

I'm attaching a patch for HttpRequestChannel.cs that avoids creating the
ManualResetEvent when nobody needs it. Ok to commit?

-Gonzalo

Index: HttpRequestChannel.cs
===
--- HttpRequestChannel.cs	(revision 154794)
+++ HttpRequestChannel.cs	(working copy)
@@ -317,16 +317,15 @@
 			AsyncCallback callback;
 			ManualResetEvent wait;
 			Exception error;
+			object locker = new object ();
+			bool is_completed;
 
 			public HttpChannelRequestAsyncResult (Message message, TimeSpan timeout, AsyncCallback callback, object state)
 			{
-CompletedSynchronously = true;
 Message = message;
 Timeout = timeout;
 this.callback = callback;
 AsyncState = state;
-
-wait = new ManualResetEvent (false);
 			}
 
 			public Message Response {
@@ -334,7 +333,13 @@
 			}
 
 			public WaitHandle AsyncWaitHandle {
-get { return wait; }
+get {
+	lock (locker) {
+		if (wait == null)
+			wait = new ManualResetEvent (is_completed);
+	}
+	return wait;
+}
 			}
 
 			public object AsyncState {
@@ -355,7 +360,6 @@
 error = error ?? ex;
 
 IsCompleted = true;
-wait.Set ();
 if (callback != null)
 	callback (this);
 			}
@@ -365,7 +369,14 @@
 			}
 
 			public bool IsCompleted {
-get; private set;
+get { return is_completed; }
+set {
+	is_completed = value;
+	lock (locker) {
+		if (is_completed && wait != null)
+			wait.Set ();
+	}
+}
 			}
 
 			public void WaitEnd ()
@@ -376,9 +387,9 @@
 	// exception to the Complete () method and allow the result to complete 'normally'.
 #if NET_2_1
 	// neither Moonlight nor MonoTouch supports contexts (WaitOne default to false)
-	bool result = wait.WaitOne (Timeout);
+	bool result = AsyncWaitHandle.WaitOne (Timeout);
 #else
-	bool result = wait.WaitOne (Timeout, true);
+	bool result = AsyncWaitHandle.WaitOne (Timeout, true);
 #endif
 	if (!result)
 		throw new TimeoutException ();
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test Suite Failures, Revision 2

[Atsushi Eno]

Hey Jonathan,

Thanks for heads up.

On 2010/04/02 2:26, Jonathan Pobst wrote:
>
> -- test-System_ServiceModel --
> 6 sporadic timeouts
> started in r154243 (Gonzalo)
> http://build.mono-project.com/GetFile.aspx?id=2257888

Gonzalo, tell me if you got some fixes. I'll stick to r154237 so far 
(after updating my repo it was blocking nunit test run there, so I have 
reverted to older version).

> -- test-System_ServiceModel_Web --
> 1 timeout started in r154243 (Gonzalo)
> 1 json failure since test suite added: r154188 (Atsushi)
> http://build.mono-project.com/GetFile.aspx?id=2257906
>
I'll have a look at JSON issue.

Atsushi Eno

___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test Suite Failures, Revision 2

[Rodrigo Kumpera]

On Thu, Apr 1, 2010 at 2:26 PM, Jonathan Pobst  wrote:

> [Updated list of test failures since last week]
>
> Hey guys!
>
> We have accumulated many test suite failures in the past month.  If you
> commit to mono, please take the time to regularly check the buildbots to
> ensure you are not breaking things.
>
> The buildbot results are available here:
> http://wrench.mono-project.com/builds
>
> Our "new" buildbots build every revision, so it's easy to track down
> where something regressed.
>
> Current Regressions  (all on SLE11 32 bit)
> ---
>
> -- test-compiler-2.0 --
> test-454.cs
> http://build.mono-project.com/GetFile.aspx?id=2257661
>
>
> -- test-corlib-2.0 --
>
> http://build.mono-project.com/GetFile.aspx?id=2257690
>
> MonoTests.System.Reflection.Emit.AssemblyBuilderTest.GetType :   #1
> regressed in r154231 (Kumpera)
>
> MonoTests.System.Reflection.Emit.ModuleBuilderTest.DefineType_Name_Null
> :   #5
> regressed in r154486 (Zoltan)
>
> MonoTests.System.Reflection.Emit.ModuleBuilderTest.TestGlobalMethods
> regressed in r154592 (Kumpera)
>
>
>
I'm working on the whole v2 and v4 regressions for corlib. Zoltan's
regression is already fixed.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] Test Suite Failures, Revision 2

[Jonathan Pobst]

[Updated list of test failures since last week]

Hey guys!

We have accumulated many test suite failures in the past month.  If you
commit to mono, please take the time to regularly check the buildbots to
ensure you are not breaking things.

The buildbot results are available here:
http://wrench.mono-project.com/builds

Our "new" buildbots build every revision, so it's easy to track down
where something regressed.

Current Regressions  (all on SLE11 32 bit)
---

-- test-compiler-2.0 --
test-454.cs
http://build.mono-project.com/GetFile.aspx?id=2257661


-- test-corlib-2.0 --

http://build.mono-project.com/GetFile.aspx?id=2257690

MonoTests.System.Reflection.Emit.AssemblyBuilderTest.GetType :   #1
regressed in r154231 (Kumpera)

MonoTests.System.Reflection.Emit.ModuleBuilderTest.DefineType_Name_Null 
:   #5
regressed in r154486 (Zoltan)

MonoTests.System.Reflection.Emit.ModuleBuilderTest.TestGlobalMethods
regressed in r154592 (Kumpera)


-- test-System_Xml_Linq-3.5 --
castdatetimes
Caused by DST time change
http://build.mono-project.com/GetFile.aspx?id=2257798


-- test-System_ServiceModel --
6 sporadic timeouts
started in r154243 (Gonzalo)
http://build.mono-project.com/GetFile.aspx?id=2257888


-- test-System_ServiceModel_Web --
1 timeout started in r154243 (Gonzalo)
1 json failure since test suite added: r154188 (Atsushi)
http://build.mono-project.com/GetFile.aspx?id=2257906


Thanks for your help in keeping Mono from regressing!

Jonathan
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test Suite Failures

[Andreas Färber]

Am 26.03.2010 um 14:50 schrieb Andreas Färber:

> Current build issue at r154271:
>
> MCS [moonlight_bootstrap] mscorlib.dll
> System/Type.cs(1570,34): error CS1501: No overload for method
> `GetType' takes `3' arguments
> System.Reflection/MemberInfoSerializationHolder.cs(74,46): error
> CS1501: No overload for method `GetType' takes `3' arguments
> Compilation failed: 2 error(s), 0 warnings
> make[8]: *** [../../class/lib/moonlight_bootstrap/tmp/mscorlib.dll]
> Error 1

For the record: `make mcs-do-clean` fixed this, `make clean` inside  
corlib was insufficient. Some dependency problem I guess.

Andreas
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test Suite Failures

[Andreas Färber]

Am 25.03.2010 um 16:14 schrieb Jonathan Pobst:

> We have accumulated many test suite failures in the past month.  If  
> you
> commit to mono, please take the time to regularly check the  
> buildbots to
> ensure you are not breaking things.
>
> The buildbot results are available here:
> http://wrench.mono-project.com/builds

Current build issue at r154271:

MCS [moonlight_bootstrap] mscorlib.dll
System/Type.cs(1570,34): error CS1501: No overload for method  
`GetType' takes `3' arguments
System.Reflection/MemberInfoSerializationHolder.cs(74,46): error  
CS1501: No overload for method `GetType' takes `3' arguments
Compilation failed: 2 error(s), 0 warnings
make[8]: *** [../../class/lib/moonlight_bootstrap/tmp/mscorlib.dll]  
Error 1

Those particular files appear to be unmodified though.

Andreas
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test Suite Failures

[Rodrigo Kumpera]

On Thu, Mar 25, 2010 at 12:14 PM, Jonathan Pobst  wrote:

> Hey guys!
>
> We have accumulated many test suite failures in the past month.  If you
> commit to mono, please take the time to regularly check the buildbots to
> ensure you are not breaking things.
>
> The buildbot results are available here:
> http://wrench.mono-project.com/builds
>
> Our "new" buildbots build every revision, so it's easy to track down
> where something regressed.
>
> Current Regressions  (all on SLE11 32 bit)
> ---
>
>
> test-mini
> simd error
> 154183 - kumpera
> http://build.mono-project.com/GetFile.aspx?id=2163467
>
> test-aot
> simd error
> 154183 - kumpera
> http://build.mono-project.com/GetFile.aspx?id=2166777
>
>
Fixed, I forgot to commit the mcs bits.
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Re: [Mono-dev] Test Suite Failures

[Zoltan Varga]

Hi,


> test-runtime
> mkbundle error
> http://build.mono-project.com/WebServices/Download.aspx?workfile_id=2166773
>
>
This is caused by mkbundle trying to use the installed mono-2.pc to compile
some C code, but it cannot be found. Adding our mono-2.pc to PKG_CONFIG_PATH
wouldn't work either, since it
references the installed dirs, i.e. /usr/local/include etc.

 Zoltan
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

[Mono-dev] Test Suite Failures

[Jonathan Pobst]

Hey guys!

We have accumulated many test suite failures in the past month.  If you
commit to mono, please take the time to regularly check the buildbots to
ensure you are not breaking things.

The buildbot results are available here:
http://wrench.mono-project.com/builds

Our "new" buildbots build every revision, so it's easy to track down
where something regressed.

Current Regressions  (all on SLE11 32 bit)
---

test-runtime
mkbundle error
http://build.mono-project.com/WebServices/Download.aspx?workfile_id=2166773

test-mini
simd error
154183 - kumpera
http://build.mono-project.com/GetFile.aspx?id=2163467

test-aot
simd error
154183 - kumpera
http://build.mono-project.com/GetFile.aspx?id=2166777

tests-verify
Mvc Error
153615 - mhabersack
http://build.mono-project.com/GetFile.aspx?id=2166784

test-compiler-2.0
test-454.cs
http://build.mono-project.com/WebServices/Download.aspx?workfile_id=2166786

test-System-2.0
LicenseManagerTests
153687 - kumpera
http://build.mono-project.com/WebServices/Download.aspx?workfile_id=2083269

test-System_Runtime_Remoting
Timeout
153687 - kumpera
http://build.mono-project.com/WebServices/Download.aspx?workfile_id=2166905

test-Microsoft_Build_Tasks-2.0
TaskBatchingTest
153687 - kumpera
http://build.mono-project.com/GetFile.aspx?id=2166925

test-Mono_C5-2.0
generics sharing error
154072 - zoltan
http://build.mono-project.com/GetFile.aspx?id=2166929

test-System_Xml_Linq-3.5
castdatetimes
153558 - atsushi
http://build.mono-project.com/WebServices/Download.aspx?workfile_id=2166934

Thanks for your help in keeping Mono from regressing!

Jonathan
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list