From: Howard B O. <ho...@ci...> - 2004-08-16 14:43:52
|
Yes, the "human readable" output format produces the summary I want to present. However, I want the more detailed output to be available too, particularly in the case where there is a failure of some sort. So I extract the detailed output, and save it in a separate file, which I then link to in my main output table. On Mon, 2004-08-16 at 04:19, Jay Turner wrote: > On Fri, Aug 13, 2004 at 02:08:34PM -0700, Howard B Owen wrote: > > I'm displaying results from running LTP. I want to provide pass/fail > > status, and a link to the test output. Most tests place their output > > after the <<<test_output>>> tag. But some place it between the previous > > test's <<<test_end>>> tag and their own <<<test_start>>> tag. This > > sucks, to be blunt. My output state machine is very upset. 8) > > > > Is this a pan issue? Or is it a test mishandling the LTP API? I don't > > have time to squint at the source enough to tell for myself at the > > moment. Does anyone have a quick pointer to where the problem may lie? > > Don't know if you've tried this already, but passing the '-p' flag (human > readable format logfiles) will give you a log file of this format: > > Test Start Time: Fri Aug 13 12:38:22 2004 > ----------------------------------------- > Testcase Result Exit Value > -------- ------ ---------- > abort01 PASS 0 > accept01 PASS 0 > access01 PASS 0 > access02 PASS 0 > access03 PASS 0 > > In addition, it will provide a summary at the tail end of the log file: > > ----------------------------------------------- > Total Tests: 807 > Total Failures: 2 > Kernel Version: 2.4.21-18.ELjg3smp > Machine Architecture: i686 > Hostname: sata.test.redhat.com > > Might be worth looking into. > > - jkt -- Howard Owen - Linux Architect "Even if you are on the right IBM Global Services - Cisco Linux track, you'll get run over if you ho...@ci... +1-408-853-1381 just sit there." - Will Rogers |