DPDK CI discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
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>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-ci] Should we keep autotest.py ?
Date: Fri, 8 Oct 2021 09:03:22 +0100	[thread overview]
Message-ID: <01fac4e3-6c15-012d-0427-0936ef537bbb@intel.com> (raw)
In-Reply-To: <CAJFAV8zruDXn1=a4+Y9NoympC8DxcAxF59skFznNjs3+mw6n+w@mail.gmail.com>

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.


  reply	other threads:[~2021-10-08  8:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 13:08 David Marchand
2021-10-08  7:30 ` David Marchand
2021-10-08  8:03   ` Ferruh Yigit [this message]
2021-10-08  9:37     ` [dpdk-ci] [dpdk-dev] " Bruce Richardson
2021-10-08 10:19     ` [dpdk-ci] " Thomas Monjalon
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01fac4e3-6c15-012d-0427-0936ef537bbb@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=aconole@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=lylavoie@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=zhaoyan.chen@intel.com \


* 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;
as well as URLs for NNTP newsgroup(s).