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.*
> -----Original Message-----
> From: pcp-bounces@xxxxxxxxxxx [mailto:pcp-bounces@xxxxxxxxxxx] On
> Behalf Of Nathan Scott
> Sent: Friday, 6 March 2015 3:17 PM
> To: Martins Innus
> Cc: PCP
> Subject: [pcp] pcp2rrdtool qa/926 tweak
>
> ...
> Also, is there a recipe for gathering this ganglia test data? I could
extract
> data from some of these hosts, and extend the test coverage here. We
> could perhaps put this recipe in the comment at the head of the test too,
for
> anyone else wanting to do this later.
|