DPDK CI discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: 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, dev <dev@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-ci] [dpdk-dev] Should we keep autotest.py ?
Date: Fri, 8 Oct 2021 10:37:09 +0100
Message-ID: <YWARRXv5CG7iO7Xj@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <01fac4e3-6c15-012d-0427-0936ef537bbb@intel.com>

On Fri, Oct 08, 2021 at 09:03:22AM +0100, Ferruh Yigit wrote:
> 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/

For me, OK to remove.

/Bruce

  reply	other threads:[~2021-10-08  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 13:08 [dpdk-ci] " David Marchand
2021-10-08  7:30 ` David Marchand
2021-10-08  8:03   ` Ferruh Yigit
2021-10-08  9:37     ` Bruce Richardson [this message]
2021-10-08 10:19     ` 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:
  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=YWARRXv5CG7iO7Xj@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --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=thomas@monjalon.net \
    --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

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git