public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Sebastian Frias <sf84@laposte.net>
To: ltp@lists.linux.it
Subject: [LTP] getrusage04 on ARM fails sometimes
Date: Tue, 26 Apr 2016 11:51:31 +0200	[thread overview]
Message-ID: <571F3A23.6070202@laposte.net> (raw)
In-Reply-To: <20160425144643.GC20158@rei.lan>

Hi,

We are wondering if other people have issues with getrusage04 LTP test.
We see it failing sometimes on our ARM platform.
It seems to happen most often when CONFIG_HZ=300 than when CONFIG_HZ=100.

When the test was introduced (https://sourceforge.net/p/ltp/mailman/message/27853271/) it did not support the "-m" parameter, which is meant to broaden the "acceptance" interval.
The "-m" parameter was added by people from ST (fd875256d6f99102e3940c4dfc6b0a8a27f4d62c), so presumably working on embedded (probably ARM) systems.
Some people are increasing that interval (https://ez.analog.com/docs/DOC-9111).

Also, according to the commit history, the test is disabled on QEMU, Xen and other environments.

Questions:
1) Does anybody else using ARM has issues with this test? Or is it just us?
2) Do you suggest that we increase the "-m" parameter?
3) Do you know of another test that could be used to double check that getrusage04 failure is a false positive?

Thanks, regards,

Sebastian



  reply	other threads:[~2016-04-26  9:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 13:25 [LTP] Issue with the reporting of failed tests Mason
2016-04-21 14:47 ` Mason
2016-04-21 15:30   ` Cyril Hrubis
2016-04-21 15:42     ` Mason
2016-04-21 17:02       ` Mason
2016-04-21 18:59         ` Mason
2016-04-22 13:29         ` Mason
2016-04-25  8:04           ` Mason
2016-04-25 11:40             ` Mason
2016-04-25 12:46               ` Mason
2016-04-25 13:31                 ` Cyril Hrubis
2016-04-25 14:24                   ` Mason
2016-04-25 14:46                     ` Cyril Hrubis
2016-04-26  9:51                       ` Sebastian Frias [this message]
2016-04-25 13:04               ` Cyril Hrubis

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=571F3A23.6070202@laposte.net \
    --to=sf84@laposte.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox