From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] lib/tst_test.c: Run test in child process
Date: Wed, 8 Jun 2016 14:30:56 +0200 [thread overview]
Message-ID: <20160608123056.GA26573@rei.lan> (raw)
In-Reply-To: <969277405.4512739.1465373864678.JavaMail.zimbra@redhat.com>
Hi!
> > diff --git a/lib/tst_test.c b/lib/tst_test.c
> > index b8ec246..eef54e4 100644
> > --- a/lib/tst_test.c
> > +++ b/lib/tst_test.c
> > @@ -220,17 +220,19 @@ void tst_vres_(const char *file, const int lineno, int
> > ttype,
> > void tst_vbrk_(const char *file, const int lineno, int ttype,
> > const char *fmt, va_list va) __attribute__((noreturn));
> >
> > -static void do_cleanup(void);
> > +static void do_test_cleanup(void)
> > +{
> > + if (tst_test->cleanup)
> > + tst_test->cleanup();
> > +}
> >
> > void tst_vbrk_(const char *file, const int lineno, int ttype,
> > const char *fmt, va_list va)
> > {
> > print_result(file, lineno, ttype, fmt, va);
> >
> > - if (getpid() == main_pid) {
> > - do_cleanup();
> > - cleanup_ipc();
> > - }
> > + if (getpid() == main_pid)
> > + do_test_cleanup();
> >
>
> Not directly related to this patch, but I noticed that we don't
> seem to cleanup_ipc if we hit TBROK outside of main test pid.
The cleanup_ipc() is intended to be executed just before the main pid
exits since it unlinks the shm file. If child TBROKs it's catched in the
check_child_status() in the parent, tst_brk() is called which will call
the cleanup_ipc().
I guess that we may close and unmap the shm even in the children but
wouldn't that happen anyway as the process exits?
> > +void tst_run_tcases(int argc, char *argv[], struct tst_test *self)
> > +{
> > + int status;
> > + char *mul;
> > +
> > + tst_test = self;
> > + TCID = tst_test->tid;
> > +
> > + do_setup(argc, argv);
> > +
> > + if (tst_test->timeout)
> > + timeout = tst_test->timeout;
>
> Can you think of a testcase where we would want to disable timeout?
At the moment I do not remember a test that would need timeout to be
turned off. And if we find that it's necessary we can always disable in
case that tst_test->timeout < 0.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2016-06-08 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 11:58 [LTP] [PATCH v2] lib/tst_test.c: Run test in child process Cyril Hrubis
2016-06-08 8:17 ` Jan Stancek
2016-06-08 12:30 ` Cyril Hrubis [this message]
2016-06-08 12:59 ` Jan Stancek
2016-06-08 13:15 ` Cyril Hrubis
2016-06-08 13:36 ` Jan Stancek
2016-06-08 13:55 ` Cyril Hrubis
2016-06-08 14:06 ` Cyril Hrubis
2016-06-08 14:31 ` Jan Stancek
2016-06-08 14:32 ` 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=20160608123056.GA26573@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