All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] times03: don't assume process initial [us]time is 0
Date: Fri, 9 Mar 2018 05:05:35 -0500 (EST)	[thread overview]
Message-ID: <179653010.6308352.1520589935610.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAEemH2c5DCNk1K-uXxeXkYi3tYyFt5rJFvEsE7R=0m_pSk+27Q@mail.gmail.com>



----- Original Message -----
> On Fri, Mar 9, 2018 at 3:29 PM, Jan Stancek <jstancek@redhat.com> wrote:
> 
> > times() runs immediately after fork(), but syscall alone
> > seems to be enough for some systems to already account ticks.
> >
> > For example on arm64 with 4.14:
> >   tst_test.c:980: INFO: Timeout per run is 0h 05m 00s
> >   times03.c:102: PASS: buf1.tms_utime = 0
> >   times03.c:105: FAIL: buf1.tms_stime = 1
> >   ...
> >
> > This patch replaces zero check with a comparison against a small
> > enough number < 5 (which should be between 5ms and 50ms depending
> > on CONFIG_HZ).
> >
> > Suggested-by: Cyril Hrubis <chrubis@suse.cz>
> > Signed-off-by: Jan Stancek <jstancek@redhat.com>
> > ---
> >  testcases/kernel/syscalls/times/times03.c | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/testcases/kernel/syscalls/times/times03.c
> > b/testcases/kernel/syscalls/times/times03.c
> > index 78d72d259ec1..c34faf5a2ff9 100644
> > --- a/testcases/kernel/syscalls/times/times03.c
> > +++ b/testcases/kernel/syscalls/times/times03.c
> > @@ -96,15 +96,15 @@ static void verify_times(void)
> >         if (times(&buf1) == -1)
> >                 tst_brk(TBROK | TERRNO, "times()");
> >
> > -       if (buf1.tms_utime != 0)
> > +       if (buf1.tms_utime > 5)
> >                 tst_res(TFAIL, "buf1.tms_utime = %li", buf1.tms_utime);
> >         else
> > -               tst_res(TPASS, "buf1.tms_utime = 0");
> > +               tst_res(TPASS, "
> > ​​
> > buf1.tms_utime > 5");
> >
> 
> ​shouldn't this ​buf1.tms_utime <= 5 ?​

You're right, the TPASS message is wrong.

> 
> 
> 
> >
> > -       if (buf1.tms_stime != 0)
> > +       if (buf1.tms_stime > 5)
> >                 tst_res(TFAIL, "buf1.tms_stime = %li", buf1.tms_stime);
> >         else
> > -               tst_res(TPASS, "buf1.tms_stime = 0");
> > +               tst_res(TPASS, "buf1.tms_stime > 5");
> >
> 
> ​here as well.
> ​
> 
> 
> >
> >         generate_utime();
> >         generate_stime();
> > --
> > 1.8.3.1
> >
> >
> ​Other than that this looks good to me. I also run this changes more than
> 100 times and ​all passed.
> 

  reply	other threads:[~2018-03-09 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  7:29 [LTP] [PATCH v2] times03: don't assume process initial [us]time is 0 Jan Stancek
2018-03-09  9:48 ` Li Wang
2018-03-09 10:05   ` Jan Stancek [this message]
2018-03-09 12:01     ` Cyril Hrubis
2018-03-09 12:17       ` Jan Stancek

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=179653010.6308352.1520589935610.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.