Hi All,
May be this can be an option for output format of LTP in future. This is
just a sample. You need to add your comments and your outlook before we
finally decide how it should look like. There are certain points which i
want to highlight:
1) We should not touch pan code for generating this output, less, we
will introduce far more bugs into pan. We can write a script which will
parse the normal LTP output file ( or log, or, failed file(s) for that
matter) and generate this output format and of course a separate output
file. Now the question arises, is, whether we should have this in:
XML ?
or HTML ?
But, whatever the case, we need to retain the original file formats and
then only parse them to generate the new format(s).
2) The option to produce this format output should be provided through
an option during ltprun, say, <runltp -F html> or <runltp -F XML>. In
normal case, it produces the original format files, otherwise the parser
invoked to create these additional file formats.
3) Ricardoś patch (applied earlier) to provide the name of Failed file
(containing the tag name and cmdline entries of failed test-cases) does
not write error info in to the same file. May be we need to produce
error info in that file as well, although it is existing in the output
file. So, the new format can also be made applicable for the failed file
as well.
** Creation of failed filed is now made mandatory by runltp
3) Even Log files generated with -l option (with or wihout -p option)
should also be able to display in this format types (tentative) as well.Now, you need to tell, what changes need to be done to this. I have plenty to suggest: 1) Start-Time should be more meaningfull. We can provide in HH:mm:SS format, 2) Test Failure can be displayed with red background colour for the user to detect failures. Or, more better to sort all red-background rows to make them appear at the beginning to display all failed tests in the beginning. ** Another thing which i have in mind is to automatically mail the test-results to a mail-id mentioned during ltp-run, say like <runltp -E [EMAIL PROTECTED]> Kindly pour your comments regarding this. We will make LTP logs/output better looking. --Regards-- SubrataTitle: Linux Test Project - Results
LTP Results (Run on DD:MM:YY-HH:mm:SS)
| Test-Name |
Command Line |
Start-Time |
Contacts |
analysis |
Initiation-Status |
Test-Output |
Duration |
Termination_type |
Termination_id |
Core File |
cutime |
cstime |
abort01 |
ulimit -c 1024;abort01 |
1189860651 |
exit |
ok |
abort01 1 PASS : Test passed |
0 |
exited |
0 |
no |
0 |
0 |
|
accept01 |
accept01 |
1189860651 |
exit |
ok |
accept01 1 PASS : bad file descriptor successful accept01 2 PASS : bad file descriptor successful accept01 3 PASS : invalid socket buffer successful accept01 4 PASS : invalid salen successful accept01 5 PASS : invalid salen successful accept01 6 PASS : no queued connections successful accept01 7 PASS : UDP accept successful |
0 |
exited |
0 |
no |
0 |
0 |
|
access01 |
access01 |
1189860651 |
exit |
ok |
access01 1 PASS : access(accessfile, F_OK) returned 0 access01 2 PASS : access(accessfile, X_OK) returned 0 access01 3 PASS : access(accessfile, W_OK) returned 0 access01 4 PASS : access(accessfile, R_OK) returned 0 |
0 |
exited |
0 |
no |
0 |
0 |
|
access03 |
access03 |
1189860651 |
exit |
ok |
access03 1 PASS : access((char *)-1,R_OK) failed as expected with errno 14 (EFAULT) : Bad address access03 2 PASS : access((char *)-1,W_OK) failed as expected with errno 14 (EFAULT) : Bad address access03 3 PASS : access((char*)-1,X_OK) failed as expected with errno 14 (EFAULT) : Bad address access03 4 PASS : access((char*)-1,F_OK) failed as expected with errno 14 (EFAULT) : Bad address access03 5 PASS : access((char*)sbrk(0)+1,R_OK) failed as expected with errno 14 (EFAULT) : Bad address access03 6 PASS : access((char*)sbrk(0)+1,W_OK) failed as expected with errno 14 (EFAULT) : Bad address access03 7 PASS : access(high_address,X_OK) failed as expected with errno 14 (EFAULT) : Bad address access03 8 PASS : access((char*)sbrk(0)+1,F_OK) failed as expected with errno 14 (EFAULT) : Bad address |
0 |
exited |
0 |
no |
0 |
0 |
|
Containers |
container_test.sh |
1189860651 |
exit |
ok |
Uts namespaces not enabled in kernel. Not running utsns tests. ipc namespaces not enabled in kernel. Not running pidns tests. |
0 |
exited |
0 |
no |
0 |
0 |
|
Numa-testcases |
numa01.sh |
1189860651 |
exit |
ok |
libnuma: Warning: /sys not mounted or no numa system. Assuming one node: No such file or directory libnuma: Warning: Cannot parse distance information in sysfs: No such file or directory Initnuma 0 WARN : non-NUMA aware kernel is running or your machine does not support numa policy or your machine is not a NUMA machine Initnuma 1 FAIL : INIT NUMA FAILED !! exitnuma 0 INFO : CLEAN: removing /tmp/ltp-3317/tst_numa.3454 incrementing stop |
1 |
exited |
1 |
no |
1 |
1 |
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
