This post summarizes the progress in the Seventh week of the coding period.
pcp-pidstat was merged with the
pcp master. My first contribution to PCP.
Finally a big moment,
pcp-pidstat getting merged into
pcp was the first milestone in the journey of GSoC.
Since last week, the man-pages(1) were set and only thing left was to write regression tests.
pcp maintains a
qa/ directory which has regression tests with a number; say N and N.out as a output file, which is checked by the
./check script present in the same directory. Regression test for pcp includes the following steps:
./new. It will create a new test with a suitable number.
pmloggerwhich contains 3-4 samples to be used for the qa. Store it into the
./remakescript. All the
./checkscript does is, it executes the commands from this script and tries to (near)match the output with the
pcpoptions to match
One of the many good things pcp APIs provides is, provision to override default
pcp options to perform different operations. After
pcp-pidstat was merged, some pcp developers tried to use it and suggested using
-p option same as the
pidstat instead of
-P. Then Nathan hinted an example about overriding default options. After looking at the example, I was able to replace that option.
So far everything looks great!
Thank you, Ryan and Nathan for the help so far. :)
That’s all folks.