qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Giusti <kgiu...@redhat.com>
Subject Re: Valgrind based soak tests fail against earlier versions of valgrind (3.2.1)
Date Thu, 04 Apr 2013 14:07:36 GMT
Hi Keith,

This patch:  http://pastebin.com/bSGjm0nN

*should* get valgrind working for older versions.  Can you try it against your 3.2.1 valgrind
and let me know (my version of valgrind is 3.5).

If running the above patch fails to suppress any errors on your system, it will prompt you
to print out a new suppression.  If that happens, can you print the suppression and send it
to me?

thanks in advance

-K

----- Original Message -----
> From: "Ken Giusti" <kgiusti@redhat.com>
> To: proton@qpid.apache.org, "keith wall" <keith.wall@gmail.com>
> Sent: Thursday, April 4, 2013 8:44:17 AM
> Subject: Re: Valgrind based soak tests fail against earlier versions of valgrind (3.2.1)
> 
> Hi Keith,
> 
> Ah, so sorry - I'll take a look.
> 
> My first instinct is to simply disable the valgrind tests for older versions,
> but let me check if I can fix the suppression in some backward compatible
> way.
> 
> /me valgrind noob.
> 
> 
> ----- Original Message -----
> > From: "Keith W" <keith.wall@gmail.com>
> > To: proton@qpid.apache.org
> > Sent: Thursday, April 4, 2013 7:26:29 AM
> > Subject: Valgrind based soak tests fail against earlier versions of
> > valgrind (3.2.1)
> > 
> > Hello
> > 
> > We are seeing a the valgrind based soak tests fail on boxes with
> > earlier versions of valgrind (3.2.1).
> > 
> >  proton_tests.soak.MessengerTests.test_star_topology_valgrind
> > ...............................................................................location
> > should start with fun: or obj:
> > ==1403== FATAL: in suppressions file
> > '/home/keith/src/live/qpid-proton/tests/python/proton_tests/valgrind.supp':
> > location should start with 'fun:' or 'obj:'
> > ==1403== exiting now.
> > 
> > Is it possible to avoid the dependency on the newer version, or get
> > config.sh to check the version of valgrind if it requires a specific
> > version?
> > 
> > Thanks in advance, Keith
> > 
> 
> --
> -K
> 

-- 
-K

Mime
View raw message