From: Cyril Hrubis <chrubis@suse.cz>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] enable pwrite for 64 bits test
Date: Thu, 30 Dec 2010 11:14:29 +0100 [thread overview]
Message-ID: <20101230101429.GC14045@saboteur.suse.cz> (raw)
In-Reply-To: <201012291844.33699.vapier@gentoo.org>
Hi!
> personally, i never use runtest. i dont believe our testers do either. i'm
> not sure what the current position is wrt to, but i dont think we should
> require people working in the syscalls tree to update random runtest lists
> whenever they add new tests.
The runtest files are used to generate automatic test runs at least here
in suse.
> if there is a runtest that says "run all syscall tests", then that sounds like
> a list that should be autogenerated by the build system.
Tried that, the problem is that quite number of the tests are same
binary just with different parameters. So just now there is a need for
runtest files.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-12-30 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 9:35 [LTP] enable pwrite for 64 bits test Vivi
2010-12-29 16:42 ` Mike Frysinger
2010-12-29 22:10 ` Garrett Cooper
2010-12-29 22:47 ` Mike Frysinger
2010-12-29 23:26 ` Garrett Cooper
2010-12-29 23:44 ` Mike Frysinger
2010-12-29 23:57 ` Garrett Cooper
2010-12-30 10:14 ` Cyril Hrubis [this message]
2011-01-15 5:39 ` Garrett Cooper
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=20101230101429.GC14045@saboteur.suse.cz \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.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