Thanks for this Mark.
> -----Original Message-----
> From: pcp-bounces@xxxxxxxxxxx [mailto:pcp-bounces@xxxxxxxxxxx] On
> Behalf Of Mark Goodwin
> ...
> commit 99af59eb2018f3fbe2080a5e783da88e9c44552f
> Author: Mark Goodwin <mgoodwin@xxxxxxxxxx>
> Date: Fri Jan 15 19:54:17 2016 +1100
>
> qa: add an archive containing a mark record for qa tests.
>
> The qa/archives/pmiostat_mark archive spans :
>
> commencing Tue Dec 1 16:00:02.042 2015
> ending Tue Dec 1 18:59:41.654 2015
>
> and the mark record is about halfway thru at 17:50:02.041
>
> Replaying from the beginning with -t 15m should return
> PM_ERR_VALUE
> at 18:00:02, i.e. when interpolating between the fetch at
> 17:45:02
> and the fetch at 18:00:02.
> ...
Is the QA test to use this still in your pipeline?
I've been thinking about this (a lot) and believe I'm moving towards Frank's
point of view. I'll add the the BZ entry when the dust settles.
My current code (running QA at the moment) produces this sort of output ...
pmiostat -a pmiostat_mark -t 15m -A 15m -z -x t
...
Tue Dec 1 17:45:00 2015 mmcblk0 0.0 0.0 0.0 0.0 0.0
0.0 0.00 0.00 0.0 0.0 0.0 0.0
Tue Dec 1 17:45:00 2015 sda 0.0 4.1 0.3 6.1 1.6
73.8 11.84 0.01 1.6 0.8 1.7 0.4
Tue Dec 1 18:15:00 2015 NODATA ? ? ? ? ?
? ? ? ? ? ? ?
Tue Dec 1 18:30:00 2015 mmcblk0 0.0 0.0 0.0 0.0 0.0
0.0 0.00 0.00 0.0 0.0 0.0 0.0
Tue Dec 1 18:30:00 2015 sda 0.0 1.7 0.4 3.6 2.5
37.3 9.90 0.01 1.7 0.6 1.8 0.3
Is that more what you'd like to see?
|