From: Francesco RUNDO <francesco.rundo@st.com>
To: naresh kamboju <naresh.kernel@gmail.com>
Cc: ltp-list@lists.sourceforge.net, maxin john <maxinbjohn@gmail.com>,
brinda_mn@yahoo.co.in, Manas Kumar Nayak <maknayak@in.ibm.com>,
Oleg Nesterov <oleg@redhat.com>,
rohit.170309@gmail.com
Subject: Re: [LTP] [FIX HTML PATCH] ltp-genhtml
Date: Thu, 18 Jun 2009 11:10:51 +0200 [thread overview]
Message-ID: <4A3A049B.2000002@st.com> (raw)
In-Reply-To: <f5a7b3810906171317j40473a95y5dfc1b89d9e25950@mail.gmail.com>
Hi,
I'm not sure about your patch.
I've introduced the usage of such env variables to support cross-build
of LTP.
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 ?
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.
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.
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.
Now, by taking into account what above mentioned, I've to suggest to do
not apply your proposal patch.
Best Regards,
Francesco
naresh kamboju wrote:
>Hi,
>
>I have noticed following issue and fixed.
>1. Kernel Version
>2. Machine Architecture.
>
>Please find the patch below and as attachment.
>
>Best regards
>Naresh Kamboju
>
>Signed-off-by: Naresh Kamboju < naresh.kernel@gmail.com >
>
>diff -Naurb a/tools/genhtml.pl b/tools/genhtml.pl
>--- a/tools/genhtml.pl 2009-04-02 12:07:28.000000000 +0530
>+++ b/tools/genhtml.pl 2009-06-18 00:33:46.000000000 +0530
>@@ -246,8 +246,12 @@
> print "<tr><td><strong>Total Test TWARN</strong></td><td><strong>
>$warn_test_counter </strong></td></tr>\n";
> print "<tr><td><strong>Total Test TRETR</strong></td><td><strong>
>$retr_test_counter </strong></td></tr>\n";
> print "<tr><td><strong>Total Test TCONF</strong></td><td><strong>
>$conf_test_counter </strong></td></tr>\n";
>-print "<tr><td><strong>Kernel Version</strong></td><td><strong>
>$ENV{KERNEL_VERSION} </strong></td></tr>\n";
>-print "<tr><td><strong>Machine Architecture</strong></td><td><strong>
>$ENV{MACHINE_ARCH} </strong></td></tr>\n";
>+print "<tr><td><strong>Kernel_Version</strong> </td> <td><strong>";
>+$kernel_version=system("uname -r"); chop($kernel_version);
>+print " $kernel_version </strong></td></tr>\n";
>+print "<tr><td><strong>Machine_Arch</strong> </td> <td><strong>";
>+$machine_arch=system("uname -m"); chop($machine_arch);
>+print " $machine_arch </strong></td></tr>\n";
> print "<tr><td><strong>Hostname</strong> </td> <td><strong>";
> $hostname=system("uname -n"); chop($hostname);
> print " $hostname </strong></td></tr></tbody></table></div></body></html>\n";
>
>
------------------------------------------------------------------------------
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
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-06-18 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 20:17 [LTP] [FIX HTML PATCH] ltp-genhtml naresh kamboju
2009-06-18 9:10 ` Francesco RUNDO [this message]
2009-06-18 15:08 ` naresh kamboju
2009-06-19 9:02 ` Francesco RUNDO
2009-06-19 10:12 ` naresh kamboju
2009-06-19 12:19 ` Francesco RUNDO
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A3A049B.2000002@st.com \
--to=francesco.rundo@st.com \
--cc=brinda_mn@yahoo.co.in \
--cc=ltp-list@lists.sourceforge.net \
--cc=maknayak@in.ibm.com \
--cc=maxinbjohn@gmail.com \
--cc=naresh.kernel@gmail.com \
--cc=oleg@redhat.com \
--cc=rohit.170309@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox