From: Petr Vorel <pvorel@suse.cz>
To: Tim Bird <tim.bird@sony.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>,
"automated-testing@lists.yoctoproject.org"
<automated-testing@lists.yoctoproject.org>
Subject: Re: [LTP] [Automated-testing] [RFC] Include runltp-ng (runltp successor) into LTP git
Date: Fri, 18 Nov 2022 20:54:26 +0100 [thread overview]
Message-ID: <Y3fi8ljdbNP/CvQ3@pevik> (raw)
In-Reply-To: <BYAPR13MB25032674327E22B588074DE0FD069@BYAPR13MB2503.namprd13.prod.outlook.com>
Hi Tim,
> Just one quick bit of feedback...
> > -----Original Message-----
> > From: automated-testing@lists.yoctoproject.org <automated-testing@lists.yoctoproject.org> On Behalf Of Andrea Cervesato via
> > lists.yoctoproject.org
> > Hi,
> > as you may know, runltp has been under bug fixing for years without
> > providing any new feature. For this reason the Perl runltp-ng
> > (https://github.com/metan-ucw/runltp-ng) was developed, providing an
> > alternative solution that wasn't completely accepted by LTP community
> > due to the choice of using Perl as the main language.
> > For this reason, a new Python runltp-ng has been developed during this
> > year, with the target to replace Perl version and the current runltp in
> > the next future. Its code can be found here:
> > https://github.com/acerv/runltp-ng
> I think this sounds like a great project, and I look forward to trying it out.
> > runltp-ng Python version provides the following features:
> > - class based architecture in Python 3.6+
> Why python 3.6+? Fuego uses a docker container with an older
> version of Debian, that defaults to Python version 3.5.3.
We support versions from 3.6 to 3.11.
We didn't want to maintain anything older.
> Is there something specifically in Python 3.6 that is required for runltp-ng?
> Could it be avoided so that runltp-ng could be backward compatible with
> older interpreters?
Andrea will give more info, there was some limitations.
FYI runltp-ng allows you to connect over SSH (i.e. running on newer host) or
test qcow image started with QEMU. We are also thinking about supporting rootfs
+ separate kernel (output of https://buildroot.org/). Not sure if this helps
you.
We actually try to encourage people to not run runltp-ng on SUT, running from
host will allow more control in case of crashed system by test.
Kind regards,
Petr
> (Sorry, but this is one of my pet peeves about the whole Python ecosystem - the lack of
> backward compatibility, and the constant need to be creating virtual environments
> for basic tools and apps.)
> -- Tim
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#1194): https://lists.yoctoproject.org/g/automated-testing/message/1194
> Mute This Topic: https://lists.yoctoproject.org/mt/94688149/3616762
> Group Owner: automated-testing+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/automated-testing/unsub [pvorel@suse.cz]
> -=-=-=-=-=-=-=-=-=-=-=-
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2022-11-18 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 15:34 [LTP] [RFC] Include runltp-ng (runltp successor) into LTP git Andrea Cervesato via ltp
2022-11-17 19:26 ` [LTP] [Automated-testing] " Bird, Tim
2022-11-18 7:39 ` Andrea Cervesato via ltp
2022-11-18 19:54 ` Petr Vorel [this message]
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=Y3fi8ljdbNP/CvQ3@pevik \
--to=pvorel@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=ltp@lists.linux.it \
--cc=tim.bird@sony.com \
/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