From: "H.J. Lu" <hjl.tools@gmail.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: Joseph Myers <joseph@codesourcery.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Florian Weimer <fweimer@redhat.com>, DJ Delorie <dj@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fw@deneb.enyo.de>,
Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH] tst: Provide test for select
Date: Wed, 24 Mar 2021 12:17:45 -0700 [thread overview]
Message-ID: <CAMe9rOpMU4QO9fkSkmW0-G462h9syb7hXs0fPSN0FfaBZm7i-Q@mail.gmail.com> (raw)
In-Reply-To: <20210322123213.58775fbd@jawa>
On Mon, Mar 22, 2021 at 4:33 AM Lukasz Majewski <lukma@denx.de> wrote:
>
> Dear Community,
>
> > This change adds new test to assess select()'s timeout related
> > functionality (the rdfs set provides valid fd - stderr - but during
> > normal program operation there is no data to be read, so one just
> > waits for timeout).
> >
> > To be more specific - two use cases are checked:
> > - if select() times out immediately when passed struct timeval has
> > zero values of tv_usec and tv_sec.
> > - if select() times out after timeout specified in passed argument
>
> Do you have any comments regarding this patch?
>
This test failed on machines with more than 40 cores:
tst-select.c:54: 1616610088.851713938s not after 1616610089.851712804s
(difference 0.999998866s)
error: 1 test failures
I was doing 3 "makec -j28 check" in parallel.
H.J.
next prev parent reply other threads:[~2021-03-24 19:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 16:46 Lukasz Majewski
2021-03-14 19:17 ` DJ Delorie
2021-03-15 9:50 ` Lukasz Majewski
2021-03-15 17:11 ` DJ Delorie
2021-03-22 11:32 ` Lukasz Majewski
2021-03-24 19:17 ` H.J. Lu [this message]
2021-03-24 19:47 ` Adhemerval Zanella
2021-03-24 20:13 ` H.J. Lu
2021-03-24 21:14 ` Adhemerval Zanella
2021-03-24 21:21 ` H.J. Lu
2021-03-24 21:24 ` Adhemerval Zanella
2021-03-24 21:35 ` Samuel Thibault
2021-03-24 21:43 ` Adhemerval Zanella
2021-03-24 22:30 ` H.J. Lu
2021-03-25 11:35 ` Adhemerval Zanella
2021-03-25 12:20 ` Andreas Schwab
2021-03-25 12:48 ` Adhemerval Zanella
2021-03-25 13:22 ` H.J. Lu
2021-03-25 13:31 ` Adhemerval Zanella
2021-03-22 19:23 ` Adhemerval Zanella
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=CAMe9rOpMU4QO9fkSkmW0-G462h9syb7hXs0fPSN0FfaBZm7i-Q@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=dj@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=lukma@denx.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).