DPDK CI discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@oss.nvidia.com>
To: "ohilyard@iol.unh.edu" <ohilyard@iol.unh.edu>,
	"ci@dpdk.org" <ci@dpdk.org>
Cc: "aconole@redhat.com" <aconole@redhat.com>
Subject: Re: [dpdk-ci] [PATCH 1/2] create_new_execution_file_from_tags: add test specifier
Date: Mon, 11 Oct 2021 17:53:32 +0000	[thread overview]
Message-ID: <DM4PR12MB5167DEB35D5E71A5D610B62CDAB59@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210924160527.45602-1-ohilyard@iol.unh.edu>

> -----Original Message-----
> From: ci <ci-bounces@dpdk.org> On Behalf Of ohilyard@iol.unh.edu
> Sent: Friday, September 24, 2021 7:05 PM
> To: ci@dpdk.org
> Cc: aconole@redhat.com; Owen Hilyard <ohilyard@iol.unh.edu>
> Subject: [dpdk-ci] [PATCH 1/2] create_new_execution_file_from_tags: add
> test specifier
> From: Owen Hilyard <ohilyard@iol.unh.edu>
> BREAKING CHANGE: --tags syntax changed
> Due to limitations of the argparse library, the tags syntax needed
> to be redone when the ability to specify individual tests was added.
> As such, the syntax has gone from "--tags core documentation" to "--tag
> core --tag documentation". This is because argparse does not allow
> multiple greedy variadic arguments in all versions.
> added syntax to force adding a specific test
> syntax: "--test nic_single_core_perf --test hello_world"
> This flag was added to help facilitate periodic testing. The list of
> tests in the template file will be ignored by this argument. This allows
> a more automated way to run tests which should not be run under normal
> circumstances, such as rte_flow, which is lightly supported in many
> NICs.
> Signed-off-by: Owen Hilyard <ohilyard@iol.unh.edu>
> ---

I suggest splitting this patch into 2 (one for modifying the tag usage, and one for adding the --test arg).


      parent reply	other threads:[~2021-10-11 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 16:05 ohilyard
2021-09-24 16:05 ` [dpdk-ci] [PATCH 2/2] guess_git_tree: edge case and style changes ohilyard
2021-10-11 17:38   ` Ali Alnubani
2021-10-11 17:53 ` Ali Alnubani [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:

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

  git send-email \
    --in-reply-to=DM4PR12MB5167DEB35D5E71A5D610B62CDAB59@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@oss.nvidia.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=ohilyard@iol.unh.edu \


* 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).