From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
Ali Alnubani <alialnu@nvidia.com>,
Aaron Conole <aconole@redhat.com>,
ci@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Should we keep autotest.py ?
Date: Fri, 08 Oct 2021 12:19:30 +0200 [thread overview]
Message-ID: <4908203.EXNKlGYlhs@thomas> (raw)
In-Reply-To: <01fac4e3-6c15-012d-0427-0936ef537bbb@intel.com>
08/10/2021 10:03, Ferruh Yigit:
> On 10/8/2021 8:30 AM, David Marchand wrote:
> > On Tue, Oct 5, 2021 at 3:08 PM David Marchand <david.marchand@redhat.com> wrote:
> >>
> >> Looking at how to add an autotest, I came upon autotest_data.py used
> >> by autotest.py which has been in DPDK for a long time.
> >>
> >> From what I see, DTS directly calls the test binary.
> >> The public CI relies on meson to invoke unit tests.
> >>
> >> Is the autotest.py script still used in some CI or can we remove it?
> >
> > Looking back in history, we lost ability to call this script with make removal.
> > So I'd say we are fine with dropping it.
> > See 3cc6ecfdfe85 ("build: remove makefiles")
> >
> > Going once.
> >
>
> I asked similar some time ago [1], I am not using it (or not aware of anything that
> depends on it), so no objection to remove it.
>
> [1]
> http://inbox.dpdk.org/dev/6f487e05-c40f-8445-247d-43f4dc3bf822@intel.com/
>
No objection.
next prev parent reply other threads:[~2021-10-08 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 13:08 [dpdk-dev] Should we keep autotest.py ? David Marchand
2021-10-08 7:30 ` David Marchand
2021-10-08 8:03 ` Ferruh Yigit
2021-10-08 9:37 ` Bruce Richardson
2021-10-08 10:19 ` Thomas Monjalon [this message]
2021-10-08 10:55 ` David Marchand
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=4908203.EXNKlGYlhs@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=alialnu@nvidia.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lylavoie@iol.unh.edu \
--cc=zhaoyan.chen@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.