Systemtap Validation

[asac, Oct 18, 2011]: you have to keep the whiteboard updated about outcomes/findings of DONE work items and about progress or issues on INPROGRESS ones. As a rule of thumb you should update your blueprints every other day - minimum. here, please document findings of the identified useful test cases, document finding of the "check is already enough", point the reader to the improved/developed test cases from the third item etc.
[aviksil, Oct 19, 2011] systemtap has extensive test cases in its testsuite covering wide range of tests. Hence it seems the existing test cases are enough already and no new test cases are required to validate the tool.
[aviksil, Oct 20, 2011]: Written an out-of-tree lava test definition with example job file that executes the systemtap testsuite. It is available here: https://code.launchpad.net/~linaro-foundations/lava-test/lava-systemtap-test
[aviksil, Oct 25, 2011]: plars plans to look at the integration after 11.10 release
[dzin, Nov 8, 2011]: break out postponed item to bug 888115. Mark as implemented.

Headline: Systemtap for ARM has been validated using distinct test cases.

Acceptance: systemtap validated for ARM by running testsuites using LAVA framework

Work items:
Identify a set of useful test cases to validate systemtap: DONE
Check if the already available test cases are enough already, if any: DONE
Improve/develop the test cases to be able to validate the tool: DONE
Create a test job at lava containing the test cases identified by previous WIs: DONE
Announce the new test case once it's integrated at Lava: POSTPONED