| To: | myllynen@xxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] pmrep: add xlsx support |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Wed, 16 Dec 2015 18:14:12 -0500 (EST) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <56712D21.4090905@xxxxxxxxxx> |
| References: | <5670184B.7000603@xxxxxxxxxx> <231833641.41636789.1450216493040.JavaMail.zimbra@xxxxxxxxxx> <56712D21.4090905@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | SqN0vtnvyNAsafMZMPNylsBKn0zilw== |
| Thread-topic: | pmrep: add xlsx support |
Hi Marko, ----- Original Message ----- > [...] > output to match PCP not sar2xls convention). A warning is printed but > the generated archive looks to be just fine: > > Use of uninitialized value in subroutine entry at sheet2pcp line 571. Hmm, that line seems to be the closing brace of a for loop, so not clear which variable that warning is referring to. :( > Since the actively developed Python XLSX modules might occasionally > change their output (e.g. a white-space or a bug fix change) then a > diff(1) based comparison might cause false alarms too often, this > sheet2pcp(1) test would actually sound like a good idea, we'd be testing > sheet2pcp(1) more as well in the process. Yep - win, win. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] Issues running QA, Nathan Scott |
|---|---|
| Next by Date: | Re: [pcp] pmatop crashes when it encounters pid >= 1000000 (#58), Lukas Berk |
| Previous by Thread: | Re: [pcp] pmrep: add xlsx support, Marko Myllynen |
| Next by Thread: | Re: [pcp] pmrep: add xlsx support, Marko Myllynen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |