pcp
[Top] [All Lists]

Re: [pcp] pcp updates - grab bag of post-3.8.0 goodies

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pcp updates - grab bag of post-3.8.0 goodies
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Mon, 20 May 2013 19:44:22 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <519AAB0E.30107@xxxxxxxxxxxxxxxx>
References: <519AAB0E.30107@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: h4A+5QnLNxJUkTSP28gkSIQ3E8lEiw==
Thread-topic: pcp updates - grab bag of post-3.8.0 goodies

----- Original Message -----
> [Ctrl-Shift-W to unwrap lines]
> Changes committed to git://oss.sgi.com/kenj/pcp.git dev
> ...

Looks good, thanks Ken.  Looking forward to that logcheck discussion,
I'm guessing/hoping that since thats using raw, non-interpolated mode
it will be able to detect this class of time-warp problem.

> commit d530360e863811dd89d249d83fcb24ccfdbe2739
> Author: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
> Date:   Fri May 17 17:30:26 2013 +1000
> 
>     qa/512 - need more careful setup
>     
>     This one needs more of the ../src environment setup before it
>     gets to the starting gates.
>     
>     It already needs libpcp_fault, so most people will continue to
>     see this test as Not Run.
> 

Should we start building this variant with each build instead of as
a separate build?  Perhaps with some old-school makefile magic of the
libpcp/{src,o32,n32,64} ilk, so that there is a libpcp/fault with the
special compilation option used?

Also worth a read for future thinking about fault injection:
http://sourceware.org/glibc/wiki/Testing/WhiteBox

Perhaps we can tackle fault injection in a less invasive manner (using
the regular library builds) with systemtap and/or dyninst someday.

cheers.

--
Nathan

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