pcp
[Top] [All Lists]

Re: JSON PMDA with indom cache changes

To: Nathan Scott <nathans@xxxxxxxxxx>, David Smith <dsmith@xxxxxxxxxx>
Subject: Re: JSON PMDA with indom cache changes
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Thu, 04 Jun 2015 07:18:24 +1000
Cc: pcp <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <2020113955.10852155.1433298140646.JavaMail.zimbra@xxxxxxxxxx>
References: <555DEF05.7030108@xxxxxxxxxx> <461406362.3814890.1432280874168.JavaMail.zimbra@xxxxxxxxxx> <55677BB7.3060805@xxxxxxxxxx> <1432466455.9615965.1433146915880.JavaMail.zimbra@xxxxxxxxxx> <2020113955.10852155.1433298140646.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
On 03/06/15 12:22, Nathan Scott wrote:
...
1052 is also still in need of some sorting love too, I haven't got to
that part yet (from my later mail).  Ken, maybe dbpmda should give us
a sort-the-names-pdu-contents option, for QA?  (see attachment to the
earlier mail I sent David on this for sample .bad)

I'm not sure what you're looking for in the "sort-the-names-pdu-contents" option ... I save the 1052.out.bad in the email, but don't have a baseline 1052.out (in my tree) to compare it to so perhaps you could send that to me by email, or I'll wait till all of this makes it into the official tree.

But if I was to guess, I would think it is more appropriate to chop, sort and paste output in a QA test (as we've done elsewhere) rather than ask dbpmda to rewrite a PDU.

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