From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] sched_rr_get_interval01 , sched_rr_get_interval02 , sched_rr_get_interval03 testcase failure
Date: Mon, 8 Jun 2020 10:52:09 -0400 (EDT) [thread overview]
Message-ID: <1210169239.15186381.1591627929151.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <BMXPR01MB23442B106F1292542BA7F85CEE850@BMXPR01MB2344.INDPRD01.PROD.OUTLOOK.COM>
----- Original Message -----
> <<<test_output>>>
> incrementing stop
> sched_rr_get_interval01 1 TBROK : sched_rr_get_interval01.c:131:
> sched_setscheduler() failed
Common cause is that you run tests in cgroup that has zero cpu.rt_runtime_us.
1. Are sched_setparam02 and sched_getscheduler01 passing?
2. Can you rerun with this patch:
https://github.com/linux-test-project/ltp/commit/94e6163082055700db700c33ed0eab537420fdaf.patch
or use strace?
next prev parent reply other threads:[~2020-06-08 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 12:19 [LTP] sched_rr_get_interval01 , sched_rr_get_interval02 , sched_rr_get_interval03 testcase failure Pankaj Vinadrao Joshi
2020-06-08 14:52 ` Jan Stancek [this message]
[not found] ` <BMXPR01MB2344728D919729E8F7F007EBEE820@BMXPR01MB2344.INDPRD01.PROD.OUTLOOK.COM>
2020-06-09 6:25 ` Jan Stancek
2020-06-09 6:39 ` Pankaj Vinadrao Joshi
2020-06-09 6:48 ` 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=1210169239.15186381.1591627929151.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