public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] Issue with the reporting of failed tests
Date: Mon, 25 Apr 2016 16:46:43 +0200	[thread overview]
Message-ID: <20160425144643.GC20158@rei.lan> (raw)
In-Reply-To: <571E28BA.8030409@free.fr>

Hi!
> Similar issue with fanotify.
> 
> Some tests are correctly marked TCONF, but some FAIL because of TWARN.
> 
> fanotify01    1  TCONF  :  fanotify01.c:348: fanotify is not configured in this kernel.
> fanotify01    2  TCONF  :  fanotify01.c:348: Remaining cases not appropriate for configuration
> fanotify01    0  TWARN  :  fanotify01.c:359: close(-1) failed
> 
> fanotify02    1  TCONF  :  fanotify02.c:237: fanotify is not configured in this kernel.
> fanotify02    2  TCONF  :  fanotify02.c:237: Remaining cases not appropriate for configuration
> fanotify02    0  TWARN  :  fanotify02.c:248: close(-1) failed
> 
> fanotify04    1  TCONF  :  fanotify04.c:280: fanotify is not configured in this kernel.
> fanotify04    2  TCONF  :  fanotify04.c:280: Remaining cases not appropriate for configuration
> fanotify04    0  TWARN  :  fanotify04.c:291: close(-1) failed

These should have been fixed in:

commit 2d8cac4caeb21ae8e5426b7c839bd5ff3896bd37
Author: Cyril Hrubis <chrubis@suse.cz>
Date:   Tue Mar 15 12:52:41 2016 +0100

    syscalls/fanotify: Fix clenaups


Not to call close(-1) in cleanup when the test exits with TCONF.

> Also the mq_* tests FAIL instead of TCONF.
> 
> mq_notify01    0  TINFO  :  (case00) START
> mq_notify01    1  TFAIL  :  mq_notify01.c:206: mq_open failed: TEST_ERRNO=ENOSYS(38): Function not implemented

Looks like nobody has run the tests with CONFIG_POSIX_MQUEUE missing from
.config, this should be easy to fix.

> As do several netns_* tests.
> 
> netns_breakns_ns_exec_ipv6_netlink 1 TINFO : ns_create    0  TINFO  :  ltp_clone_quick: errno=EINVAL(22): Invalid argument
> netns_breakns_ns_exec_ipv6_netlink 1 TBROK : unable to create a new network namespace

These should be fixed as well.


-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2016-04-25 14:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 13:25 [LTP] Issue with the reporting of failed tests Mason
2016-04-21 14:47 ` Mason
2016-04-21 15:30   ` Cyril Hrubis
2016-04-21 15:42     ` Mason
2016-04-21 17:02       ` Mason
2016-04-21 18:59         ` Mason
2016-04-22 13:29         ` Mason
2016-04-25  8:04           ` Mason
2016-04-25 11:40             ` Mason
2016-04-25 12:46               ` Mason
2016-04-25 13:31                 ` Cyril Hrubis
2016-04-25 14:24                   ` Mason
2016-04-25 14:46                     ` Cyril Hrubis [this message]
2016-04-26  9:51                       ` [LTP] getrusage04 on ARM fails sometimes Sebastian Frias
2016-04-25 13:04               ` [LTP] Issue with the reporting of failed tests 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=20160425144643.GC20158@rei.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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