From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] ltp test add reboot function
Date: Fri, 21 Aug 2020 14:23:48 +0200 [thread overview]
Message-ID: <20200821122348.GA31841@dell5510> (raw)
In-Reply-To: <CAF12kFuE=4-T=eitwSb0F3fkGLLsmM3VEg4VNbioqJt2JiAEww@mail.gmail.com>
Hi Cixi,
> Hi ALL:
> I want to add a reboot function in LTP for my team write a memory page
> related case?
> and need reboot to make the memory cache or some likely it pure clear.
> So I want to add a tst_needs_reboot. when it was set, reboot the
> machine and continue
> run test from the point before.
> I think this requirement is meaningful? So can you give me some advise?
IMHO setup for reboot has been usually handled outside of LTP (in frameworks
which use LTP), because without any more capable runner [*] reboot would just
stop testing. I'm not saying it's not possible, but requires more thinking. At
least I'd add some variable which would prevent boot (and thus tst_brk TCONF
would be issued for this test).
I wonder what other think about it.
Kind regards,
Petr
[*] runltp is dead, but even Cyril's not yet upstreamed runltp-ng [1] and other
plans [2] does not handle reboot either. It'd have to be some service which can
pick-up the state.
[1] https://github.com/metan-ucw/runltp-ng
[2] https://people.kernel.org/metan/towards-parallel-kernel-test-runs
next prev parent reply other threads:[~2020-08-21 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 2:29 [LTP] [RFC] ltp test add reboot function Cixi Geng
2020-08-21 12:23 ` Petr Vorel [this message]
2020-08-24 7:42 ` Cyril Hrubis
2020-08-25 1:52 ` Cixi Geng
2020-08-28 13:06 ` Cyril Hrubis
2020-08-28 15:37 ` Bird, Tim
2020-09-03 1:48 ` Cixi Geng
2020-09-03 3:13 ` Bird, Tim
2020-09-03 9:24 ` Cyril Hrubis
2020-09-30 1:55 ` Cixi Geng
2020-09-30 14:05 ` Cyril Hrubis
2020-09-30 16:01 ` Bird, Tim
2020-10-01 11:03 ` 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=20200821122348.GA31841@dell5510 \
--to=pvorel@suse.cz \
--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