From: Szabolcs Nagy <nsz@port70.net>
To: Ryan Gardner <ryan.p.gardner@boeing.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH 1/3 libc-test] functional:time:clock_nanosleep test
Date: Wed, 6 Nov 2024 08:38:20 +0100 [thread overview]
Message-ID: <20241106073820.GJ2724612@port70.net> (raw)
In-Reply-To: <20241105224437.67-1-ryan.p.gardner@boeing.com>
* Ryan Gardner <ryan.p.gardner@boeing.com> [2024-11-05 22:44:35 +0000]:
> Testing of musl API against POSIX 2008 standard.
>
> Tests added:
>
> - EINTR is returned when sleep is interupted by a signal
> - ENOTSUP is returned when clock_id specifies an unsupported clock
> - EINVAL is returned when tv_nsec is out of range
> - EINVAL is returned when clock_id specifies an unknown clock
this is technically not futureproof as new clocks may be introduced
it's a common issue i dont have a good solution for.
but i think it's fine to pick an int for now.
> - EINVAL is returned when clokc_id specifies the CPU-time clock of calling thread
> - rmtp is set to the remaining unslept time when interupted.
> - time elapses as expected
>
> References:
> - https://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_nanosleep.html
>
> Signed-off-by: Ryan Gardner <ryan.p.gardner@boeing.com>
thanks
patches look good. but it will take a week or two
for me to be able to test and apply them.
next prev parent reply other threads:[~2024-11-06 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 22:44 Ryan Gardner
2024-11-05 22:44 ` [musl] [PATCH 2/3 libc-test] functional:time:timer_delete test Ryan Gardner
2024-11-05 22:44 ` [musl] [PATCH 3/3 libc-test] functional:time:timer_settime test Ryan Gardner
2024-11-06 7:38 ` Szabolcs Nagy [this message]
2024-11-07 4:39 [musl] [PATCH 1/3 libc-test] functional:time:clock_nanosleep test Gardner, Ryan P
2024-11-10 11:45 ` Szabolcs Nagy
2024-11-13 11:51 ` Szabolcs Nagy
2024-11-15 5:16 Gardner, Ryan P
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=20241106073820.GJ2724612@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
--cc=ryan.p.gardner@boeing.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).