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
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
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
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
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
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
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 kump...@gmail.com
Subject: Re: [Mono-dev] Test suite failures (Mono 2.10.2)
To: Kocsis L?szl
mailto:kump...@gmail.com
Subject: Re: [Mono-dev] Test suite failures (Mono 2.10.2)
To: Kocsis L?szl? kocsis1...@gmail.com mailto:kocsis1...@gmail.com
Cc: mono-devel-list@lists.ximian.com
mailto:mono-devel-list@lists.ximian.com
Message-ID: banlktinxujqsmhyu8jy48jxetzcxzfj...@mail.gmail.com
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
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,
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.comwrote:
Hi,
I'm encountering some test failures with the Mono 2.10.2 source
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
12 matches
Mail list logo
