Re: [LTP] [FIX HTML PATCH] ltp-genhtml

[Francesco RUNDO <francesco.rundo@st.com>]

[-- Attachment #1.1: Type: text/plain, Size: 4360 bytes --]

Hi Naresh,

thanks for your reply. Below some considerations:

naresh kamboju wrote:

>Hi Francesco,
>
>  
>
>>In fact, in case the results of LTP session was related to cross-execution, the >infiormation about KERNEL_VERSION and MACHINE_ARCHITECTURE have to >be referred to the target and not to the host. Do you agree ?
>>    
>>
>Yes.
>I agree with you.
>I have been using LTP for Target Board executions not on Host Machine.
>As per my understating KERNEL_VERSION and MACHINE_ARCHITECTURE are
>should come from env right?
>
Yes.


>But I could not print these variables in HTML file.
>

Why not ?
By means of (before to run genhtml.pl on the HOST):
export KERNEL_VERSION=" xxxxxxxxxxxxxxxx"
export MACHINE_ARCH=" xxxxxxxxxxxxxxxxxxxxx"
you will be able to export on the final HTML file the info contained in 
the above env variables.
The attached HTML log shows a typical summary (I report only subset of 
info related to the env variables).

>Please refer the results published in LTP download page for 31-May-2009 release.
>http://sourceforge.net/project/platformdownload.php?group_id=3382
>
>
>LTP Results:
>
>ltp-full-20090531_results_kernel-2.6.18-128.el5_architecture-ppc64.tgz
>ltp-full-20090531_results_kernel-2.6.18-128.el5_architecture-x86_64.tgz
>ltp-full-20090531_results_kernel-2.6.18-128.el5PAE_architecture-i386.tgz
>ltp-full-20090531_results_kernel-2.6.23.13_architecture-ia64.tgz
>ltp-full-20090531_results_kernel-2.6.27.19-5-default_architecture-i386.tgz
>
>None of the above results got printed these two KERNEL_VERSION and
>MACHINE_ARCHITECTURE variables in HTML.
>

Probably because they haven't been defined the env variables.

>
>
>  
>
>>With your fix, by using "uname -r" and "uname -m", to avoid to report wrong >information, you have to run the "genhtml.pl" script over the target system because if >you run the genhtml.pl on the host, you will get wrong information about the kernel >version and machine architecture.
>>    
>>
>No.
>As per my understanding to make generic script “uname -r" and "uname
>-m" are best way of use. All the target Machines are wont have full
>“env” support to extract KERNEL_VERSION and MACHINE_ARCHITECTURE info.
>Ofcourse my target Machine can not extract these variables.
>

No env variables have to be processed in the target. The env variables 
will be used on the HOST execution of genthml.pl.

>
>"uname -r" and "uname -m" are from target not from Host I guess.
>Because runltp script will runs on target so obviously genhtml.pl will
>run when –g option is  specified. “ #sh runltp –g
>ltp-full-results-file.html”
>  
>
>>Moreover, the assumption to run genhtml.pl over the target is not safe as often the target >systems are embedded systems which do not support PERL.
>>    
>>
>
>Yes. That is true.
>When we run runltp with –g option to create HTML file the person using
>this option should have knowledge that this script will use PERL
>script if there is no PERL no HTML file will generate right?
>  
>

No, with the usage of env variables on the "genhtml.pl", you can have 
HTML file even though PERL is not supported on your target. This is an 
advantage!

Moreover, you can manage and process "off-line" LTP report without 
having the risk to add in the report HOST information instead of TARGET 
ones.

>  
>
>>With the fix I've proposed and accepted, the LTP-user by means of the simple env >variables, can define the right information to be reported on the LTP results table about >kernel version and machine architecture.
>>    
>>
>I have attached my HTML output file after and before patch.
>Please share your commands for ltp executions and results HTML file
>and other files.
>Before and after your patch.
>
The steps I follow are simply:

1) runltp >> LTP.log (run on the TARGET platform);

2)  export KERNEL_VERSION=" xxxxxxxxxxxxxxxx"
     export MACHINE_ARCH=" xxxxxxxxxxxxxxxxxxxxx"
     ...................... (run on the HOST platform)

3) genhtml.pl LTP.log LTP.html (run on the HOST platform);

In this way I avoid to make assumptions about TARGET requirements (PERL, 
HTML, etc...).

The piece of attached LTP-log.html shows what I got.

I confirm my opinion to keep the current policy to generate HTML summary 
info.

Best Regards,
FR



[-- Attachment #1.2: Type: text/html, Size: 6120 bytes --]

[-- Attachment #2: LTP-log.html --]
[-- Type: text/html, Size: 1848 bytes --]

[-- Attachment #3: Type: text/plain, Size: 332 bytes --]

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects

[-- Attachment #4: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list