From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] Add env variable as workaround for test issues in VMs
Date: Mon, 27 Apr 2020 03:31:22 -0400 (EDT) [thread overview]
Message-ID: <951270734.10286613.1587972682386.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200427053125.GA21164@dell5510>
----- Original Message -----
> Hi Martin,
>
> > Timer tests often fail on sleep overrun when LTP is running inside a VM.
> > The main cause is usually that the VM doesn't get enough CPU time to wake
> > up
> > the test process in time.
> Cannot we detect presence of "hypervisor" in flags in /proc/cpuinfo?
> I though it was quite reliable for detecting VM.
We have tst_is_virt().
I see these tests fail frequently on ppc and s390, so I'm all for
some switch that would make it more forgiving if running under virt.
next prev parent reply other threads:[~2020-04-27 7:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 15:04 [LTP] [PATCH] Add env variable as workaround for test issues in VMs Martin Doucha
2020-04-27 5:31 ` Petr Vorel
2020-04-27 7:31 ` Jan Stancek [this message]
2020-04-27 7:41 ` Petr Vorel
2020-04-27 8:49 ` Li Wang
2020-04-27 9:06 ` Jan Stancek
2020-04-27 9:19 ` Petr Vorel
2020-04-27 9:23 ` Martin Doucha
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=951270734.10286613.1587972682386.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox