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 <kump...@gmail.com>: > 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ó <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 <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 <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://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 >> >> <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 >> >>> 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