pcp
[Top] [All Lists]

Re: [pcp] pmlogextract Indom Corruption

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pmlogextract Indom Corruption
From: Tom Yearke <tyearke@xxxxxxxxxxx>
Date: Wed, 04 Dec 2013 18:45:57 -0500
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <529F9E35.3000801@xxxxxxxxxxxxxxxx>
References: <529CDA04.7050605@xxxxxxxxxxx> <529F9E35.3000801@xxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
Yes, so far we've only seen this issue when using the -S and -T options. Running some of the original archives through pmlogextract without the time window arguments gave the expected output, even when using a time window with those archives could produce corrupted output.

Including the archive in the QA suite is fine with us! Thanks for looking into the issue!

Tom

On 12/4/2013 4:27 PM, Ken McDonell wrote:
On 03/12/13 06:05, Tom Yearke wrote:
Hello,

We are currently experiencing a problem with pmlogextract producing
archives with corrupted instance domain definitions.

G'day Tom.

Yep, your test case exposes a bug. I don't expect this to be too hard to fix (but I haven't started to look at the source code yet!).

Can I ask if you're _only_ seeing this when using the the time window arguments -S and -T?

Also, may we have your permission to include the node_archive archive in the PCP QA suite so this problem is demonstrably fixed and does not regress?



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