All of lore.kernel.org
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] runtest/ipc: Add some IPC syscalls test-cases
Date: Thu, 27 Jun 2013 15:24:23 +0200	[thread overview]
Message-ID: <20130627132422.GA21560@rei> (raw)
In-Reply-To: <CA+icZUW2hCKtEV-yvYSDrnuVW=MmB0ywTvKTPnStqWgmiAhKmg@mail.gmail.com>

Hi!
> >> Add IPC syscalls test-cases from "runtest/syscalls" file also to
> >> "runtest/ipc" for people interested in running IPC tests only.
> >>
> >> Run via './runltp -f ipc'.
> >>
> >> Signed-off-by: Sedat Dilek<sedat.dilek@gmail.com>
> >> ---
> >>   runtest/ipc | 60
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>   1 file changed, 60 insertions(+)
> >
> >
> > NAK. Duplication is generally a bad idea.
> > This have the side effect of running the same tests twice for people that
> > run ipc and syscalls test scenarios.
> >
> 
> The background of this was an issue in Linux-Next.
> The ipc test-cases were fine, but syscalls test-cases revealed that
> sth. was wrong in that Linux-Next release.
> For me it was not clear to also test the syscalls.
> 
> So, what is with the idea of a "runtest/syscalls-ipc" file (my
> original "v1" patch, this here is "v2")?

I think that we can go with the v1 for now and figure out something
better for the new test execution framework. Are you OK with that?

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2013-06-27 13:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1372336933-2770-1-git-send-email-sedat.dilek@gmail.com>
     [not found] ` <51CC37E2.20304@ti.com>
2013-06-27 13:09   ` [LTP] [PATCH] runtest/ipc: Add some IPC syscalls test-cases chrubis
     [not found]     ` <51CC3C3B.2020803@ti.com>
2013-06-27 13:28       ` chrubis
     [not found]   ` <CA+icZUW2hCKtEV-yvYSDrnuVW=MmB0ywTvKTPnStqWgmiAhKmg@mail.gmail.com>
2013-06-27 13:24     ` chrubis [this message]

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=20130627132422.GA21560@rei \
    --to=chrubis@suse.cz \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=sedat.dilek@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.