All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: Petr Vorel <pvorel@suse.cz>
Cc: Joerg Vehlow <joerg.vehlow@aox.de>,
	automated-testing@lists.yoctoproject.org, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 3/3] configure: Integrate open posix testsuite configure
Date: Mon, 01 Aug 2022 08:16:10 +0100	[thread overview]
Message-ID: <87pmhkfm1p.fsf@suse.de> (raw)
In-Reply-To: <YuQXnCgSjBT1mGFH@pevik>

Hello,

Petr Vorel <pvorel@suse.cz> writes:

> Hi Joerg,
>
> [ Cc automated-testing@lists.yoctoproject.org ]
>
>> From: Joerg Vehlow <joerg.vehlow@aox.de>
>
>> This changes the default installation location
>> of the open posix testsuite from
>> $prefix
>> to
>> $prefix/testcases/open_posix_testsuite
> I need to have a deeper look on this patchset next week.
> But it looks to me strange, that running LTP top level configure causes
> installation into /opt/ltp/testcases/open_posix_testsuite/, but after running
> ./configure in testcases/open_posix_testsuite make install goes by default to
> /opt/openposix_testsuite.
>
> Also openposix does not use LTP API, when we're touching it, wouldn't it make
> more sense to put it into separate git repository? IMHO that would cause work
> for other people (clone separate git, need to fix CI and tools which are using
> it), but openposix embedded in LTP always looked strange to me.

I wouldn't be against this based on my anecdotal experience.

I don't recall a specific time these tests found a kernel bug. They
sometimes find issues with glibc, but there is usually a debate as to
how to interpret the spec instead of a clear error on glibc's part. Most
often the test is broken.

So I'd say these tests are almost useless for kernel testing. I also
think they often misinterpret the POSIX spec or have some basic logic
error.


-- 
Thank you,
Richard.

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-08-01  7:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27  5:33 [LTP] [PATCH v2 0/3] openposix: Fix installation file layout Joerg Vehlow
2022-07-27  5:33 ` [LTP] [PATCH v2 1/3] openposix: Fix existence test for local flag-files Joerg Vehlow
2022-07-29 17:16   ` Petr Vorel
2022-08-23 10:03   ` Petr Vorel
2022-07-27  5:33 ` [LTP] [PATCH v2 2/3] openposix: Setup autoconf and fix installation layout Joerg Vehlow
2022-08-29  5:49   ` Petr Vorel
2022-08-30 11:00   ` Richard Palethorpe
2022-07-27  5:33 ` [LTP] [PATCH v2 3/3] configure: Integrate open posix testsuite configure Joerg Vehlow
2022-07-29 17:23   ` Petr Vorel
2022-08-01  7:16     ` Richard Palethorpe [this message]
2022-08-30  9:59       ` Li Wang
2022-08-03  4:45     ` Joerg Vehlow
2022-08-29 16:42   ` Petr Vorel
2022-08-30 11:01   ` Richard Palethorpe
2022-08-30 11:37     ` Petr Vorel
2022-08-26  8:49 ` [LTP] [PATCH v2 0/3] openposix: Fix installation file layout Petr Vorel

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=87pmhkfm1p.fsf@suse.de \
    --to=rpalethorpe@suse.de \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=joerg.vehlow@aox.de \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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.