public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
To: ltp-list@lists.sourceforge.net
Cc: sachinp@linux.vnet.ibm.com, iranna.ankad@in.ibm.com, svishuku@in.ibm.com
Subject: [LTP] [risrajak@linux.vnet.ibm.com: [Ltp-commits] [Git] ltp updated.]
Date: Thu, 1 Apr 2010 12:53:05 +0530	[thread overview]
Message-ID: <20100401072305.GC13796@linux.vnet.ibm.com> (raw)

Hi All,

For those who does not subscribed to ltp-commits list.

This is the new file which will be updated every month by maintainer. While
testing during the month if anyone get a chance to test on h/w or distro which i
could not cover due to time availability please send me a patch will include as
hotfixes and that can be helpful for each one us during whole month to refer.

-Rishi

----- Forwarded message from Rishi kesh K Rajak <risrajak@linux.vnet.ibm.com> -----

Date: Thu,  1 Apr 2010 07:14:26 +0000
From: Rishi kesh K Rajak <risrajak@linux.vnet.ibm.com>
To: ltp-commits@lists.sourceforge.net
Subject: [Ltp-commits] [Git] ltp updated.

The branch, next, has been updated
       via  aabf191024aacc91784593b0d3f8d5fa37434b25 (commit)
      from  f50539e0bcb0f9bab88101ce40a8e09a1d76d4a9 (commit)


- Log -----------------------------------------------------------------
commit aabf191024aacc91784593b0d3f8d5fa37434b25
Author: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>
Date:   Thu Apr 1 12:43:27 2010 +0530

    Added a new file called result where maintainer need to provide the result on which he has run before releasing the tar ball for month end release.
    
    Signed-off-by: Rishikesh K Rajak <risrajak@linux.vnet.ibm.com>

-----------------------------------------------------------------------

Summary of changes:
 result |   96 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 96 insertions(+), 0 deletions(-)
 create mode 100644 result

diff --git a/result b/result
new file mode 100644
index 0000000..78db428
--- /dev/null
+++ b/result
@@ -0,0 +1,96 @@
+This file contains for corresponding monthly release results. it will alwats help to refer this file and come to know about known failures.
+
+
+ltp-full-20100331 Result pon various Arch:
+
+On x86_64 machine with RHEL5.4(2.6.18-164.el5):
+*****************************************************
+
+Result Log file:
+===============
+eventfd01                      FAIL       4    
+syslog07                       FAIL       1    
+syslog08                       FAIL       1    
+mtest06                        FAIL       255  
+su01                           FAIL       1    
+hugemmap04                     FAIL       2    
+hugeshmat01                    FAIL       6    
+hugeshmat02                    FAIL       6    
+hugeshmat03                    FAIL       2    
+hugeshmctl01                   FAIL       6    
+hugeshmctl02                   FAIL       6    
+hugeshmctl03                   FAIL       2    
+hugeshmdt01                    FAIL       6    
+hugeshmget01                   FAIL       2    
+hugeshmget02                   FAIL       6    
+hugeshmget03                   FAIL       6    
+hugeshmget05                   FAIL       2    
+mail                           FAIL       2    
+
+
+Result Output file:
+==================
+syslog07    1  TFAIL  :  Higher level messages are not logged.
+check_netns_enabled    1  TFAIL  :  unshare syscall smoke test failed: errno=EINVAL(22): Invalid argument
+mail_tests::mail02    2  TFAIL  :  Test #2: Mailer-Deamon failed to report delivery failure. Reason:
+mail_tests::mail05    5  TFAIL  :  Test #5: mail failed to carbon copy user mail_test. Reason:
+
+
+On ppc64 machine with RHEL5.4(2.6.18-164.el5):
+*****************************************************
+
+Result Log file:
+===============
+cct01                         FAIL       1    
+eventfd01                      FAIL       4    
+fdatasync02                    FAIL       1    
+syslog07                       FAIL       1    
+syslog08                       FAIL       1    
+mtest06                        FAIL       255  
+mmapstress03                   FAIL       1    
+su01                           FAIL       1    
+cron_deny01                    FAIL       1    
+
+
+Result Output file:
+==================
+acct01      1  TFAIL  :  attempting to assign acct file to device: expected failure but got okay return
+fdatasync02    2  TFAIL  :  Unexpected results for file descriptor to a special file ; returned 0 (expected -1), errno 0 (expected 22)
+syslog07    1  TFAIL  :  Higher level messages are not logged.
+mmapstress03    1  TFAIL  :  Test failed
+check_netns_enabled    1  TFAIL  :  unshare syscall smoke test failed: errno=EINVAL(22): Invalid argument
+
+
+
+On s390x machine with RHEL5.4(2.6.18-164.el5):
+*****************************************************
+
+Result Log file:
+===============
+eventfd01                      FAIL       4    
+keyctl01                       FAIL       1    
+rt_sigsuspend01                FAIL       11   
+timer_getoverrun01             FAIL       1    
+timer_gettime01                FAIL       1    
+su01                           FAIL       1    
+cron_allow01                   FAIL       1    
+
+
+
+Result Output file:
+==================
+keyctl01    2  TFAIL  :  KEYCTL_REVOKE got unexpected errno: errno=EINVAL(22): Invalid argument
+timer_getoverrun01    1  TFAIL  :  Block 1: test 0 FAILED... errno = 22 : Invalid argument
+timer_gettime01    1  TFAIL  :  Block 1: test 0 FAILED... errno = 22 : Invalid argument
+check_netns_enabled    1  TFAIL  :  unshare syscall smoke test failed: errno=EINVAL(22): Invalid argument
+
+
+
+On x86_64 machine with SLES11GA(2.6.27.19-5-default):
+*****************************************************
+
+Result Log file:
+===============
+eventfd2_03                    FAIL       1    
+utimensat01                    FAIL       1    
+ftest04                        FAIL       1    


hooks/post-receive
-- 
ltp

------------------------------------------------------------------------------
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-commits mailing list
Ltp-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-commits

----- End forwarded message -----

-- 
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-04-01  7:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100401072305.GC13796@linux.vnet.ibm.com \
    --to=risrajak@linux.vnet.ibm.com \
    --cc=iranna.ankad@in.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=sachinp@linux.vnet.ibm.com \
    --cc=svishuku@in.ibm.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