Re: [Evolution-hackers] checking Evolution with valgrind

2008-03-29 Thread Patrick Ohly 
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 - sorry! I was hoping
  that some other developer would perhaps be motivated to use valgrind to
  analyse some of these problems.
 
 I run Evolution and E-D-S under valgrind occasionally but haven't made a
 regular habit of it.  I'll try to start doing that regularly.

Great, here's a good reason to fire it up:
http://bugzilla.gnome.org/show_bug.cgi?id=524964

Hint: your changes seem to be involved in the use-after-free and ensuing
crash found in the nightly testing ;-)

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, but it could easily be a week or more.

The tests still produce new valgrind leak reports for which I don't have
suppression rules; in particular the potentially lost reports seem to
be a bit random. Currently I'm still in the ignore leaks mode and just
suppress anything that I find.

-- 
Bye, Patrick Ohly
--  
[EMAIL PROTECTED]
http://www.estamos.de/

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] checking Evolution with valgrind

2008-03-29 Thread Matthew Barnes 
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, but it could easily be a week or more.

Sign me up, please.

Not sure how responsive I'll be at fixing leaks as they emerge, but I'd
like to stay informed at least.

Thanks for your efforts here, by the way.  It's very much appreciated.

Matthew Barnes

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers

Re: [Evolution-hackers] checking Evolution with valgrind

2008-03-29 Thread Patrick Ohly 
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 time only two days have passed since
  the tests started to fail, but it could easily be a week or more.
 
 Sign me up, please.
 
 Not sure how responsive I'll be at fixing leaks as they emerge, but I'd
 like to stay informed at least.

Thanks for volunteering.

As an example, the attached email was marked in red in my inbox due to
an incoming filter which checks for failed. evolutiontrunk is the
build step of the latest Evolution source. If it fails, then the other
steps are attempted with whatever did compile or is left from a previous
compilation. The rationale is that if building the Evolution GUI fails,
EDS testing would still run.

client-api and syncevolution are the repository checkouts of these
two components; compile, well, compiles them. When that fails, no
tests are run. evolution is the part where EDS and the SyncEvolution
client are tested - this is what we want to succeed. The rest of the
email can be ignored.

 Thanks for your efforts here, by the way.  It's very much appreciated.

Thanks for your kind words.

-- 
Bye, Patrick Ohly
--  
[EMAIL PROTECTED]
http://www.estamos.de/
---BeginMessage---
http://www.estamos.de/runtests/2008-03-29-10-00/head-evolution-trunk-minimal

evolutiontrunk successful
client-api successful
syncevolution successful
compile successful
dist skipped: disabled in configuration
evolution:  CLIENT_TEST_ALARM=1200 CLIENT_TEST_LOG= 
CLIENT_TEST_EVOLUTION_PREFIX=file:///tmp/runtests/head/work/databases 
run_garnome /home/patrick/evo-svn/gtk+2.0 
/tmp/runtests/head/tmp/evolutiontrunk-result valgrindcheck.sh ./client-test 
Client::Source: failed (return code 35072)
scheduleworld skipped: disabled in configuration
egroupware skipped: disabled in configuration
synthesis skipped: disabled in configuration
funambol skipped: disabled in configuration

/home/patrick/bin/runtests.py
--client-tag
r_tested
--configure
--enable-static-cxx LDFLAGS=-Wl,--as-needed --prefix=/usr
--tmp=/tmp/runtests/head/tmp
--workdir=/tmp/runtests/head/work
--resultdir=/home/patrick/runtests/2008-03-29-10-00/head-evolution-trunk-minimal
--resulturi=http://www.estamos.de/runtests/2008-03-29-10-00/head-evolution-trunk-minimal
--shell=run_garnome /home/patrick/evo-svn/gtk+2.0 
/tmp/runtests/head/tmp/evolutiontrunk-result
--evosvn=trunk=/home/patrick/evo-svn
--enable
evolutiontrunk
--enable
compile
--enable
evolution
--test-prefix=valgrindcheck.sh
--from
[EMAIL PROTECTED]
--to
[EMAIL PROTECTED]
---End Message---
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers