| To: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pmcc.py bug? |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 29 May 2014 20:45:11 -0400 (EDT) |
| Cc: | pcp <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <5386E607.2020007@xxxxxxxxxx> |
| References: | <5386E607.2020007@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | Emjy5twpwf5BsODV6Du9Lt0dD3KqeQ== |
| Thread-topic: | pmcc.py bug? |
Hi Mark, ----- Original Message ----- > pmcc doesn't seem to update it's metric values after each fetch beyond > the first, but I may be calling it incorrectly. Here's a simple program > demonstrating the issue, and a simple patch to pmcc.py that fixes it > (but introduces a memory leak?). So is this a bug or am I not using pmcc > correctly? Thanks for any help ... Mark. Sorry, got distracted yesterday - I'm seeing similar things, will dig into it some today. In happy news, I found the pmOptions stuff Just Works (tm) with pmcc cos MetricCache sub-classes pmContext - I'll post a new QA script soon that shows an example use case. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] python pmExtractValue segfault, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] Dropping machines from my QA farm, Nathan Scott |
| Previous by Thread: | pmcc.py bug?, Mark Goodwin |
| Next by Thread: | pcp updates: discovery (dave), python (stan & self.), misc coverity & other fixes, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |