[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241106073820.GJ2724612@port70.net>
Date: Wed, 6 Nov 2024 08:38:20 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: Ryan Gardner <ryan.p.gardner@...ing.com>
Cc: musl@...ts.openwall.com
Subject: Re: [PATCH 1/3 libc-test] functional:time:clock_nanosleep test
* Ryan Gardner <ryan.p.gardner@...ing.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@...ing.com>
thanks
patches look good. but it will take a week or two
for me to be able to test and apply them.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
