From: Cyril Hrubis <chrubis@suse.cz>
To: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [RFC] utstest.h
Date: Thu, 26 Nov 2009 15:13:46 +0100 [thread overview]
Message-ID: <20091126141346.GA7306@saboteur.suse.cz> (raw)
In-Reply-To: <20091120125347.GA4858@schrodinger.suse.cz>
Hi!
> > I've been looking at sources for usctest.h again today (lib/parse_opts.c) and I
> > still have the feeling that this is badly written/broken code and should be
> > fixed but as there are thousands of tests that uses usctest interface we should
> > be careful when touching these sources. So IMHO the best approach is to change
> > one thing at the time and see if this was a good move.
> >
> > So let's start with TEST_PAUSE macro. Accordingly to comment in the header,
> > this expands to the code that waits for SIGUSR1 signal (and this is not
> > generaly true). This macro is expanded to the int usc_global_setup_hook()
> > function. The function forks the program accordingly to STD_COPIES and
> > accordingly STD_PAUSE it sleeps for a SIGUSR1 or not (all forked instances); it
> > also changes program segment size with sbrk().
> >
> > Looking into the test sources, this is called when the test starts in order to
> > implement test parameters "-c n" (run n copies concurently) and "-p" (pause
> > test) and system variable USC_TP_SBRK. Do we need these parameters or any of
> > them? If you convice me that these parameters are usefull I would gladly clean
> > up and document code that implements TEST_PAUSE, otherwise I would vote for
> > removing them (or at least the useless ones).
> >
>
> Okay, let me put it like this. Are parameters introduced by TEST_PAUSE really
> used for anything? Would anybody cry if there where removed? Would be patch
> removing them accepted and merged into CVS?
>
Anybody out there? I would really like to clean up and simplify the test interface.
--
metan
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-11-26 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 15:16 [LTP] [RFC] utstest.h Cyril Hrubis
2009-11-20 12:53 ` Cyril Hrubis
2009-11-26 14:13 ` Cyril Hrubis [this message]
[not found] ` <364299f40911260622s4e5ae3c5j555b922a7b85f4b0@mail.gmail.com>
2009-11-30 13:50 ` Cyril Hrubis
[not found] ` <1259853101.5085.36.camel@subratamodak.linux.ibm.com>
[not found] ` <alpine.DEB.2.00.0912031014590.4647@sleepy>
2009-12-04 14:58 ` Cyril Hrubis
[not found] ` <20091203152731.GA10251@refried.org>
2009-12-04 14:54 ` 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=20091126141346.GA7306@saboteur.suse.cz \
--to=chrubis@suse.cz \
--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