Re: [LTP] [PATCH] runtest/ipc: Add some IPC syscalls test-cases

[chrubis@suse.cz]

Hi!
> >>> 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.
> > Hmm, this is a valid point.
> >
> > Thinking of the ideal way, it may be more data driven framework with a
> > list of all tests anotated with some group labels. I noted this for the
> > planned testdriver rewrite.
> >
> 
> We can easily support this with existing infrastructure if we add some 
> structure to the test case tags.
> For instance on runtest/syscalls, one could use:
> msgctl01_ipc
> msgctl02_ipc
> ...
>
> Then when calling runltp, one can use -s option to filter tests cases, 
> e.g. ./runltp -f syscalls -s '*_ipc'
> 
> At Texas Instruments we use following convention for TAG names
> <AREA>_<SCOPE>_<TYPE>_<ID>
> 
> 

That is no go, at least here we have database of testruns for different
distributions and renaming the testcases tags will break the regression
detection. So I would preffer solution that adds a metadata without
renaming the current test tags. The problem is that ltp-pan and runltp
are so horribly outdated and unmaintaned that adding functionality to
these is out of question.

-- 
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