This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Proposal for small addition to testsuite output
In followup to various chats at OLS about adding reporting on snapshot test
execution for systemtap to 'labrat', I've been looking at the minimum amount
of changes that would be needed to get enough metadata in the report to
satisfy the requirements of labrat's reporting infrastructure.
Although the initial thought was to provide a wrapper script for the testsuite
execution that would generate an output file that is in labrat-format already,
I instead decided that it is probably more useful to have the extra metadata
recorded in the currently generated systemtap.log file, and perform the
wrapper operation on the reporting end. The main reason for this is that we
hope to be able to support systemtap in full using the labrat client scripts.
That would make it unnecessary to do any encapsulation.
The three piece of information that I'd like to have added to the output are:
- The name (date) of the snapshot being tested
- The "uname -a" output for the host the testsuite is being executed on
- The content of the distribution release/version file:
/etc/fedora-release for Fedora
/etc/redhat-release for Red Hat
/etc/suse-release for SuSE
/etc/debian_version for Debian/Ubuntu
The preference would be to have them listed near the very top of the output
log, if at all possible.
I'll ask Wenji to prepare a patch for this, and I'll send private email to the
people who are currently running the snapshot testsuite with information on
where results can be uploaded.
Aside from this, I am currently finalizing the code on the reporting server to
provide historical data on a per-test level, to assist with trend analysis of
test executions. During our talks at OLS, that was raised as an important
feature-to-have for labrat.
Cheers,
Kris