From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: LTP <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] sigaction:16-1: leave it untested on the Linux kernel less than 2.6.22
Date: Tue, 6 Aug 2013 11:30:38 +0200 [thread overview]
Message-ID: <20130806093037.GA24437@rei> (raw)
In-Reply-To: <578718909.13087059.1375776716081.JavaMail.root@redhat.com>
Hi!
> > While I'm completly fine with workarounds for broken kernels in Linux
> > part of the LTP I'm a bit reluctant to add them into the open posix
> > testsuite. Has anybody different opinion?
>
> I agree when it comes to modifying testcases, but having a list
> of testcases which are known to fail (and avoid running them)
> on linux is also handy.
>
> How about something like top-level Makefile.linux, which would
> build everything as it does now, but after that it disables
> those which are known to fail? For example by replacing something.run-test
> with script that prints message and returns UNTESTED.
That sounds reasonable to me.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2013-08-06 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 2:15 [LTP] [PATCH] sigaction:16-1: leave it untested on the Linux kernel less than 2.6.22 Wanlong Gao
2013-08-05 9:46 ` chrubis
[not found] ` <578718909.13087059.1375776716081.JavaMail.root@redhat.com>
2013-08-06 9:30 ` chrubis [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-14 2:25 Peng Haitao
2013-11-14 9:33 ` Jan Stancek
2013-11-14 12:29 ` chrubis
[not found] ` <187658148.31700134.1384433325925.JavaMail.root@redhat.com>
2013-11-14 12:55 ` chrubis
[not found] ` <5285EB6C.9000107@cn.fujitsu.com>
[not found] ` <5296D114.4070507@cn.fujitsu.com>
2013-11-28 14:15 ` chrubis
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=20130806093037.GA24437@rei \
--to=chrubis@suse.cz \
--cc=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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