| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, 'Nathan Scott' <nathans@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp2rrdtool qa/926 tweak |
| From: | Martins Innus <minnus@xxxxxxxxxxx> |
| Date: | Fri, 06 Mar 2015 10:19:20 -0500 |
| Cc: | 'PCP' <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <001601d057d6$59f487c0$0ddd9740$@internode.on.net> |
| References: | <502488780.21978731.1425609530465.JavaMail.zimbra@xxxxxxxxxx> <1426675409.22052119.1425615446159.JavaMail.zimbra@xxxxxxxxxx> <001601d057d6$59f487c0$0ddd9740$@internode.on.net> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 |
Ken, On 3/6/15 1:25 AM, Ken McDonell wrote: As a note to everyone ... If you add data files (including archives) to the QA suite, it is _really_ helpful to first create a script that creates the data files (even if it will only run in some exotic environment), checkin the script, then use the script to make the data file(s) and finally checkin the data file(s). If the script needs special love to run it, encode this in the GNUmakefile with a target that will never be "made" by the usual build. This way everyone can see how the data file was created (it is sometimes the only way to judge if a particular QA test is producing the expected output), and as needs dictate new versions of the data files can be generated. For examples see qa/src/mk* and qa/archives/mk.* Thanks for the tip. I found a mk* file that I modified for this purpose. Martins |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: pcp2rrdtool qa/926 tweak, Martins Innus |
|---|---|
| Next by Date: | pcp2rrdtool QA support scripts, Martins Innus |
| Previous by Thread: | RE: [pcp] pcp2rrdtool qa/926 tweak, Ken McDonell |
| Next by Thread: | Re: pcp2rrdtool qa/926 tweak, Martins Innus |
| Indexes: | [Date] [Thread] [Top] [All Lists] |