public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Peng Haitao <penght@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH v2] ltp-pan.c: fix error of Total Tests
Date: Thu, 17 May 2012 13:04:53 +0800	[thread overview]
Message-ID: <4FB486F5.3040100@cn.fujitsu.com> (raw)
In-Reply-To: <CAGH67wSv02CxLFBDDuO8dRWNp03AmHmnYqTd3UN2mQkF8SO8ZQ@mail.gmail.com>


Garrett Cooper said the following on 2012-5-17 12:39:
>> <<<test_start>>>
>> tag=exit_quickly stime=1337251363
>> cmdline="exit 1"
>> contacts=""
>> analysis=exit
>> <<<test_output>>>
>> <<<execution_status>>>
>> initiation_status="pan(17520): execvp of 'exit' (tag exit_quickly) failed.  errn                                                 o:2  No such file or directory"
> 
> I suppose it would have worked, had this actually been a command and
> not a shell built-in. Could you please replace 'exit 1' with 'false'?
> 

The log is as follows:

<<<test_start>>>
tag=exit_quickly stime=1337259686
cmdline="false"
contacts=""
analysis=exit
<<<test_output>>>
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=0
<<<test_end>>>

# cat /opt/ltp/results/LTP_RUN_ON-2012_May_17-21h_01m_26s.log
Test Start Time: Thu May 17 21:01:26 2012
-----------------------------------------
Testcase                       Result     Exit Value
--------                       ------     ----------
aok                            PASS       0
donotexist                     FAIL       2
exit_quickly                   FAIL       1
true                           PASS       0

-----------------------------------------------
Total Tests: 4
Total Failures: 2
Kernel Version: 2.6.32-220.el6.x86_64
Machine Architecture: x86_64
Hostname: RHEL6U2-x86-64


Thanks.

-- 
Best Regards,
Peng Haitao


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2012-05-17  5:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F2CE53D.9030908@cn.fujitsu.com>
2012-05-16 14:53 ` [LTP] [PATCH] ltp-pan.c: fix error of Total Tests Cyril Hrubis
     [not found]   ` <1337219962-5782-1-git-send-email-penght@cn.fujitsu.com>
     [not found]     ` <4FB45E98.3010506@cn.fujitsu.com>
2012-05-17  2:31       ` [LTP] [PATCH v2] " Garrett Cooper
2012-05-17  2:33         ` Wanlong Gao
2012-05-17  2:39           ` Garrett Cooper
2012-05-17  2:40             ` Garrett Cooper
2012-05-17  2:47               ` Peng Haitao
2012-05-17  4:39                 ` Garrett Cooper
2012-05-17  5:04                   ` Peng Haitao [this message]
2012-05-17  5:52                     ` Garrett Cooper
2012-05-17 11:05                       ` Cyril Hrubis

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=4FB486F5.3040100@cn.fujitsu.com \
    --to=penght@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=yanegomi@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