pcp
[Top] [All Lists]

Possible QA issue in _valgrind_clean_assert

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>, Dave Brolley <brolley@xxxxxxxxxx>
Subject: Possible QA issue in _valgrind_clean_assert
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Thu, 12 Feb 2015 00:01:06 -0500 (EST)
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1936499254.4052190.1423716457141.JavaMail.zimbra@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: KraDaXrjZF5pVx58AVzX+2nHHwxUUw==
Thread-topic: Possible QA issue in _valgrind_clean_assert
Hi,

"qa/666: use $_valgrind_clean_assert for pmmgr under microscope"
is now merged.  It looks OK to me & 666 passes with it here.  Dave
made a note that he's observed this, however...

666 - output mismatch (see 666.out.bad)
18a19,21
> ==9712== could not unlink 
> /tmp/vgdb-pipe-from-vgdb-to-9712-by-root-on-brolley-t530
> ==9712== could not unlink 
> /tmp/vgdb-pipe-to-vgdb-from-9712-by-root-on-brolley-t530
> ==9712== could not unlink 
> /tmp/vgdb-pipe-shared-mem-vgdb-9712-by-root-on-brolley-t530

... could you take a look & work it out together?  I'm punting its
something specific to Dave's valgrind version/installation.  Also,
note I've had to update the valgrind-suppress change from the SASL
fix; syntax used was not available for older valgrinds (e.g. 3.6.0
on rhel6).

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>