From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it, linuxtestproject.agent@gmail.com
Subject: Re: [LTP] OpenPOSIX: Add common entry point function for all tests
Date: Fri, 17 Apr 2026 16:44:45 +0200 [thread overview]
Message-ID: <20260417144445.GA426937@pevik> (raw)
In-Reply-To: <d5b21bfa-5fd7-4e2d-b1c0-c89c6b509dbb@suse.cz>
Hi Martin,
> Hi!
I overlooked your reply (please my following one with diff).
> On 4/17/26 15:09, Petr Vorel wrote:
> > Hi Martin,
> > > Hi Martin,
> > > On Thu, 16 Apr 2026, Martin Doucha wrote:
> > > > OpenPOSIX: Add common entry point function for all tests
> > > > Add a new shared source file implementing the main() function and rename
> > > > the existing main() functions in test case sources to test_main(). This
> > > > allows adding custom debug code to all test cases at once.
> > > [...]
> > > > diff --git a/testcases/open_posix_testsuite/conformance/interfaces/pthread_create/assertions.xml b/...
> > > > - NOTE: that the thread in which main() was originally invoked is different
> > > > + NOTE: that the thread in which test_main() was originally invoked is different
> > > This changes verbatim POSIX specification text. The assertions.xml files
> > > quote the POSIX standard, which defines behaviour relative to main() — the C
> > > entry point, not an LTP-internal function name. Revert these hunks in both
> > > pthread_create/assertions.xml and pthread_exit/assertions.xml.
> > +1
> This "issue" is nonsense. I've checked the XML files and the assertions are
> still correct as is regardless of renaming a few functions. The
> pthread_create() and pthread_exit() specification applies special treatment
> to the main thread and adding one more function call between the main()
> function and the test code does not change that.
I understood that spec talks about main() as a specific C startup function.
But ok, I was probably wrong.
> > > > diff --git a/.../aio_write/9-2.c b/.../aio_write/9-2.c
> > > > +int test_main(int argc, char** argv)
> > > s/char** argv/char **argv/ to match the style used everywhere else.
> This typo is actually in conformance/interfaces/strcpy/1-1.c (line 23793 of
> the patch). Please change the test_main() signature to this during merge:
> int test_main(int argc PTS_ATTRIBUTE_UNUSED, char **argv
> PTS_ATTRIBUTE_UNUSED)
OK, fixed and merged. Thanks!
> I don't think it makes sense to send another 1MB patch to fix one line.
That's why I sent another reply with diff.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-04-17 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260416144213.27221-1-mdoucha@suse.cz>
2026-04-16 18:36 ` [LTP] OpenPOSIX: Add common entry point function for all tests linuxtestproject.agent
2026-04-17 13:09 ` Petr Vorel
2026-04-17 13:35 ` Martin Doucha
2026-04-17 14:44 ` Petr Vorel [this message]
2026-04-17 14:33 ` Petr Vorel
2026-04-16 18:53 ` [LTP] [PATCH] " Petr Vorel
2026-04-17 0:30 ` Li Wang via ltp
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=20260417144445.GA426937@pevik \
--to=pvorel@suse.cz \
--cc=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--cc=mdoucha@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox