All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raghavendra Kakarla <Raghavendra.Kakarla@inedasystems.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: LTP tests
Date: Mon, 9 Nov 2015 11:55:20 +0000	[thread overview]
Message-ID: <1447070120093.83542@inedasystems.com> (raw)
In-Reply-To: <1447065096992.47595@inedasystems.com>


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

Hi All,


I built the ltp_20150119 in the yocto build system.


But  while running the test cases, some tests are failed.


I am attaching the document for that failed test cases to this mail.


Please confirm me these test cases are failed due to the yocto rfs or kernel.


Thanks in advance.


Regards,

Raghavendra K.

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

[-- Attachment #2: LTP_RUN_LOG --]
[-- Type: application/octet-stream, Size: 2145 bytes --]

Test Start Time: Wed Oct 28 08:32:05 2015
-----------------------------------------
Testcase                       Result     Exit Value
--------                       ------     ----------
bind02                         FAIL       2    
chdir01A                       FAIL       1       
getrusage03                    FAIL       2      
inotify03                      FAIL       11       
fanotify01                     FAIL       36   
fanotify02                     FAIL       36  
fanotify04                     FAIL       36    
mq_notify01                    FAIL       1    
mq_notify02                    FAIL       1    
mq_open01                      FAIL       1    
mq_timedreceive01              FAIL       1    
mq_timedsend01                 FAIL       1    
mq_unlink01                    FAIL       1     
readahead02                    FAIL       33     
remap_file_pages01             FAIL       7    
rt_sigaction01                 FAIL       10   
rt_sigprocmask01               FAIL       35      
rt_sigsuspend01                FAIL       14      
sync_file_range01              FAIL       1    
syslog01                       FAIL       1    
syslog02                       FAIL       1    
syslog03                       FAIL       1    
syslog04                       FAIL       1    
syslog05                       FAIL       1    
syslog06                       FAIL       1    
syslog07                       FAIL       1    
syslog08                       FAIL       1    
syslog09                       FAIL       1    
syslog10                       FAIL       1    
utimensat01                    FAIL       1    
gf01                           FAIL       1    
gf14                           FAIL       1    
gf15                           FAIL       1       
gf18                           FAIL       1       
quota_remount_test01           FAIL       2    
isofs                          FAIL       1     
dio13                          FAIL       1       
mtest06_2                      FAIL       255     
thp02                          FAIL       2    
thp03                          FAIL       2    
   

       reply	other threads:[~2015-11-09 11:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1447065096992.47595@inedasystems.com>
2015-11-09 11:55 ` Raghavendra Kakarla [this message]
2015-11-10  3:08   ` LTP tests Yi Zhao

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=1447070120093.83542@inedasystems.com \
    --to=raghavendra.kakarla@inedasystems.com \
    --cc=yocto@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.