pcp
[Top] [All Lists]

Re: More cleverer QA config needed? (was Re: [pcp] NSS/NSPR Testing Stat

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: More cleverer QA config needed? (was Re: [pcp] NSS/NSPR Testing Status)
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 30 Nov 2012 06:33:22 +1100
Cc: Dave Brolley <brolley@xxxxxxxxxx>, pcp@xxxxxxxxxxx
In-reply-to: <1030669710.35428511.1354156473966.JavaMail.root@xxxxxxxxxx>
References: <1030669710.35428511.1354156473966.JavaMail.root@xxxxxxxxxx>
On Wed, 2012-11-28 at 21:34 -0500, Nathan Scott wrote:
> ...
> This actually raises another interesting twist on the QA config
> issue - this passes for me with some PCP_VER_3611 variants (ie.
> built --without-secure-sockets) but fails otherwise.  Suggests
> we need to consider doing something more sophisticated for the
> QA tests with NSS/NSPR dependencies - pkg-config(1) for PCP?

Check src/check_fault_injection.c ... I think this demonstrates a
precedent for checking on the fly if a particular flavour of libpcp is
installed, and this is used as a guard in the scripts that want to
exercise that feature, e.g. 476.

This could be also used to choose between alternate expected output
files, possibly in combination with PCP_VER checking.

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