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

Harry Wilkinson hwilkinson at mdsol.com
Fri Jun 24 04:01:19 EDT 2011

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.


On 23 June 2011 20:05, Steve Bjorg <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://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>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
>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20110624/d6968b8c/attachment.html 

More information about the Mono-devel-list mailing list