pcp
[Top] [All Lists]

Re: [pcp] More Python induced QA pain

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] More Python induced QA pain
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Tue, 26 Jul 2016 00:09:40 -0400 (EDT)
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>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: qLnL731FQGM9qdYPVa5VJn24gWoQhw==
Thread-topic: More Python induced QA pain

----- Original Message -----
> [...]
> It would be nice if the linux PMDA fix Nathan is chasing for the same
> QA failure would trigger this, namely pmwebd closing the connection.
> Nathan?

qa/662 tickles the bug every time for me.  There's two issues, one around
return the code from a dynamic pmns refresh routine, the other related to
metric help text lookup.

See how current master goes for you now Ken, you should see the 100% fail
for that test reduce back to the original set (like the IPv6 issue, etc).

cheers.

--
Nathan

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