pcp
[Top] [All Lists]

Re: More Python induced QA pain

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: More Python induced QA pain
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Mon, 25 Jul 2016 22:51:36 -0400
Cc: PCP <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <02053e52-b708-e106-b4dc-6d63bcdb29b8@xxxxxxxxxxxxxxxx>
References: <578E9E23.9090904@xxxxxxxxxxxxxxxx> <y0mh9bdkdzj.fsf@xxxxxxxx> <5796812B.6090409@xxxxxxxxxxxxxxxx> <20160725214336.GH5274@xxxxxxxxxx> <57969592.3050402@xxxxxxxxxxxxxxxx> <20160726012720.GA12088@xxxxxxxxxx> <02053e52-b708-e106-b4dc-6d63bcdb29b8@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi -

On Tue, Jul 26, 2016 at 12:10:34PM +1000, Ken McDonell wrote:
> Frank, in case it helps I've attached the 662.full failure from the F24 
> machine.

Interesting.  Yours diverges from mine pretty early on: during the
post-context-creation enumeration of the metrics.  As a SWAG, maybe
something in pmcd/etc. is now taking too long to enumerate the PMNS
and causing libpcp level timeouts?  Maybe try running pmwebd in the
662 test case with -D$something.

- FChE

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