[PATCH v10] Fix time/tst-cpuclock1 intermitent failures

H.J. Lu hjl.tools@gmail.com
Sat Jul 11 16:31:54 GMT 2020


On Sat, Jul 11, 2020 at 7:45 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Fri, Jul 10, 2020 at 4:10 PM Tulio Magno Quites Machado Filho
> <tuliom@ascii.art.br> wrote:
> >
> > Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org> writes:
> >
> > > OK for master. I'd like to see this fixed in glibc 2.32.
> > > Thank you for fixing the test case!
> > >
> > > Reviewed-by: Carlos O'Donell <carlos@redhat.com>
> >
> > Pushed as 04deeaa9ea74b0679dfc9d9155a37b6425f19a9f.
> >
>
> support/tst-timespec failed on i686 and x32:
>
> Test case 10
> tst-timespec.c:312: numeric comparison failure
>    left: 0 (0x0); from: support_timespec_check_in_range
> (check_cases[i].expected, check_cases[i].observed,
> check_cases[i].lower_bound, check_cases[i].upper_bound)
>   right: 1 (0x1); from: check_cases[i].result
> Test case 11
>

Usage of long may be the problem.

-- 
H.J.


More information about the Libc-alpha mailing list