public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@google.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: LTP test failures on current kernels (latest -git and -mm)
Date: Sat, 15 Apr 2006 11:32:36 -0700	[thread overview]
Message-ID: <44413C44.4010309@google.com> (raw)

I'm seeing a lot of LTP failures in current kernels. Is this just LTP
being horribly broken? Or are mailine kernels broken?

I've never been keen on it's "expected failure" model, but this does
seem to be excessive. Get very similar failures from -mm and mainline.

2.6.17-rc1-mm2: 
http://test.kernel.org/abat/27722/001.ltp.test/results/ltp.failures

2.6.17-rc1-git9:
http://test.kernel.org/abat/28423/001.ltp.test/results/ltp.failures

accept01    1  FAIL  :  bad file descriptor ; returned -454050240 
(expected -1), errno 0 (expected 9)
capset02    4  BROK  :  Unexpected signal 15 received.
clone06     0  WARN  :  sprintf() failed
clone06     1  BROK  :  Unexpected signal 11 received.
connect01    1  FAIL  :  bad file descriptor ; returned -435334536 
(expected -1), errno 0 (expected 9)
dup06       1  FAIL  :  Not enough files duped
dup06       2  FAIL  :  Test failed.
fcntl23     1  FAIL  :  fcntl(tfile_15730, F_SETLEASE,F_RDLCK) Failed, 
errno=11 : Resource temporarily unavailable
getdtablesize01    2  FAIL  :  0 != 1023
getpeername01    1  FAIL  :  bad file descriptor ; returned -1209263248 
(expected -1), errno 0 (expected 9)
getsockname01    1  FAIL  :  bad file descriptor ; returned -1209283664 
(expected -1), errno 0 (expected 9)
getsockopt01    1  FAIL  :  bad file descriptor ; returned -457777152 
(expected -1), errno 0 (expected 9)
ioperm02    1  FAIL  :  Unexpected results for Invalid I/O address ; 
returned 0 (expected -1), errno 0 (expected errno  22)
kill05      0  INFO  :  WARNING: shared memory deletion failed.
listen01    1  FAIL  :  bad file descriptor ; returned 0 (expected -1), 
errno 0 (expected 9)
mlockall02    1  CONF  :  mlockall02 did not FAIL as expected.This may 
be okay if you are running Red Hat Enterprise Linux 3 (RHEL)
mlockall02    2  CONF  :  mlockall02 did not FAIL as expected.This may 
be okay if you are running Red Hat Enterprise Linux 3 (RHEL)
mincore01    4  FAIL  :  call succeeded unexpectedly
recvmsg01    1  FAIL  :  bad file descriptor ; returned -1056444352 
(expected -1), errno 0 (expected 9)
sendmsg01    1  FAIL  :  bad file descriptor ; returned -1 (expected 
-1), errno 14 (expected 9)
setitimer01    1  FAIL  :  old timer value is not equal to expected value
setregid02    7  FAIL  :  setregid(65535, -1) failed (1) but did not set 
the expected errno (22).
setregid02    8  FAIL  :  setregid(-1, 65535) failed (1) but did not set 
the expected errno (22).
setsockopt01    1  FAIL  :  bad file descriptor ; returned 13 (expected 
-1), errno 0 (expected 9)
socket01    4  FAIL  :  raw open as non-root ; returned -1 (expected 
-1), errno 93 (expected 94)
socket01    6  FAIL  :  UDP stream ; returned -1 (expected -1), errno 93 
(expected 94)
socket01    7  FAIL  :  TCP dgram ; returned -1 (expected -1), errno 93 
(expected 94)
socket01    9  FAIL  :  ICMP stream ; returned -1 (expected -1), errno 
93 (expected 94)
socketpair01    4  FAIL  :  raw open as non-root ; returned -1 (expected 
-1), errno 93 (expected 94)
socketpair01    8  FAIL  :  TCP dgram ; returned -1 (expected -1), errno 
93 (expected 94)
socketpair01   10  FAIL  :  ICMP stream ; returned -1 (expected -1), 
errno 93 (expected 94)
writev03    1  FAIL  :  Got error EFAULT
writev03    0  INFO  :  block 1 FAILED
writev03    2  FAIL  :  Got error EFAULT
writev03    0  INFO  :  block 2 FAILED
writev03    3  FAIL  :  Got error EFAULT
writev03    0  INFO  :  block 3 FAILED
writev04    1  FAIL  :  Got error EFAULT
writev04    0  INFO  :  block 1 FAILED
writev04    2  FAIL  :  Got error EFAULT
writev04    0  INFO  :  block 2 FAILED
writev04    3  FAIL  :  Got error EFAULT
writev04    0  INFO  :  block 3 FAILED
INFO: pan reported some tests FAIL

                 reply	other threads:[~2006-04-15 18:32 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=44413C44.4010309@google.com \
    --to=mbligh@google.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox