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
To fix the problem I added a check to see if the item being docked is
the same as the first item in the tab group, if so, modifies the
insertion index appropriately because trying to insert the item before
itself in the group causes the float problem. Since its status was
AutoHide it is still
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
I am getting this exception on exit when using Lion and running the latest
2.10.2. I've tried calling Environment.Exit(0) and mono_jit_cleanup during
app shutdown. But doing either of those leads to other exceptions.
Hopefully there is a solution for this situation. Thanks,
Duane
0
This is fixed in git by rodrigo iirc.
-g
On Fri, Jun 24, 2011 at 3:02 PM, Duane Wandless du...@wandless.net wrote:
I am getting this exception on exit when using Lion and running the latest
2.10.2. I've tried calling Environment.Exit(0) and mono_jit_cleanup during
app shutdown. But doing
I thought it was fixed with this commit:
https://github.com/mono/mono/commit/2b487789c8e3dcc3fbbcb16bb0268f88718cf8d0
However, I'm using this code and still seeing the exception. Just now
in _wapi_handle_unref_full.
Duane
On Fri, Jun 24, 2011 at 3:04 PM, Geoff Norton gro...@gmail.com wrote:
Is there a g_error printed prior to the crash?
-g
On Fri, Jun 24, 2011 at 3:12 PM, Duane Wandless du...@wandless.net wrote:
I thought it was fixed with this commit:
https://github.com/mono/mono/commit/2b487789c8e3dcc3fbbcb16bb0268f88718cf8d0
However, I'm using this code and still seeing the
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
Nothing that I can find.
On Fri, Jun 24, 2011 at 3:14 PM, Geoff Norton gro...@gmail.com wrote:
Is there a g_error printed prior to the crash?
-g
On Fri, Jun 24, 2011 at 3:12 PM, Duane Wandless du...@wandless.net
wrote:
I thought it was fixed with this commit:
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
14 matches
Mail list logo
