public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: Anthony Ton <anthony.ton@ericsson.com>, Min Guo <min.guo@intel.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] tcore.exp
Date: Fri, 19 Mar 2010 10:17:33 +0530	[thread overview]
Message-ID: <20100319044733.GB27760@linux.vnet.ibm.com> (raw)
In-Reply-To: <E0B6230F32558E43951AF1B0DEBF98102119D20EDD@EUSAACMS0714.eamcs.ericsson.se>


Adding the original developer in cc to know opinion about this changes.

-Rishi
On Thu, Mar 18, 2010 at 09:16:50PM -0400, Anthony Ton wrote:
>Hi Ltp team, 
>Hi LTP tea,
> 
>It appears that the proc check_fpu in tcore.exp has an error when the expect
>can't find the expected string "xmm$num …".  In the timeout block, the code read
> 
>fail "fail to check the xmm value(timeout)"
> 
>In my humble opinion, it should be
> 
>send_user "fail to check the xmm value(timeout)"
> 
>The script crashes with error message:
> 
>(gdb) invalid command name "fail"
>    while executing
>"fail "fail to check the xmm value(timeout)""
>    invoked from within
>"expect -nobrace -re {xmm5[      ]+{f = .*}+[    ]+{f = .*}} {
>                        set buf $expect_out(0,string)
>                } timeout {
>                    fail "fail to check the xmm value(..."
>    invoked from within
>>"expect {
>                -re "xmm$num\[\t \]+\{f \= .*\}+\[\t \]+\{f \= .*\}" {
>                        set buf $expect_out(0,string)
>                }
>                timeout {
>                    fail "fail to check t..."
>    (procedure "check_fpu" line 7)
>    invoked from within
>"check_fpu 5"
>    (file "/opt/anthony/ltp/testcases/bin//tcore.exp" line 137)
> 
>Please let me know how to fix this error.
>> 
>Thanks,
>Anthony 

> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev

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


-- 
Thanks & Regards
Rishi
LTP Maintainer
IBM, LTC, Bangalore
Please join IRC #ltp @ irc.freenode.net

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2010-03-19  4:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19  1:16 [LTP] tcore.exp Anthony Ton
2010-03-19  4:47 ` Rishikesh K Rajak [this message]
2010-03-22  6:41 ` Rishikesh K Rajak
2010-03-22 21:06   ` Anthony Ton

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=20100319044733.GB27760@linux.vnet.ibm.com \
    --to=risrajak@linux.vnet.ibm.com \
    --cc=anthony.ton@ericsson.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=min.guo@intel.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