On Sat, 2008-03-29 at 12:32 -0400, Matthew Barnes wrote:
> On Sat, 2008-03-29 at 14:46 +0100, Patrick Ohly wrote:
> > My offer still stands: I could add interested developers to CC of the
> > emails which report nightly test success or failure. I look at the
> > results rather sporadically; this ti
On Sat, 2008-03-29 at 14:46 +0100, Patrick Ohly wrote:
> My offer still stands: I could add interested developers to CC of the
> emails which report nightly test success or failure. I look at the
> results rather sporadically; this time only two days have passed since
> the tests started to fail, b
On Wed, 2008-03-26 at 15:03 -0400, Matthew Barnes wrote:
> On Wed, 2008-03-26 at 19:33 +0100, Patrick Ohly wrote:
> > > The best is that if you could track it down to Evolution, file a
> bug
> > > with the valgrind traces and CC me there.
> >
> > ... this is exactly what I won't have time for - so
On Wed, 2008-03-26 at 19:33 +0100, Patrick Ohly wrote:
> I'm afraid it won't help Evolution much apart from catching regressions
> from now on, because ...
>
> > The best is that if you could track it down to Evolution, file a bug
> > with the valgrind traces and CC me there.
>
> ... this is exac
On Tue, 2008-03-25 at 23:44 +0530, Srinivasa Ragavan wrote:
> On Tue, 2008-03-25 at 20:58 +0100, Patrick Ohly wrote:
> > as part of the nightly testing that I mentioned recently I now also
> > started to run evolution-data-server and the test program under
> > valgrind, including --leak-check=yes.
On Tue, 2008-03-25 at 20:58 +0100, Patrick Ohly wrote:
> Hello,
>
> as part of the nightly testing that I mentioned recently I now also
> started to run evolution-data-server and the test program under
> valgrind, including --leak-check=yes. That covers the file backends for
> calendar and contact
