From: Aaron Conole <aconole@redhat.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: David Marchand <david.marchand@redhat.com>,
Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>,
Kevin Traynor <ktraynor@redhat.com>
Subject: Re: [PATCH v4] app/test: add support for skipping tests
Date: Wed, 04 Oct 2023 11:13:17 -0400 [thread overview]
Message-ID: <f7t4jj6h14i.fsf@redhat.com> (raw)
In-Reply-To: <CAJvnSUCD9qjdXOi6xesVbta0dOSsZ5v8218XJ18R7iBg80wxjA@mail.gmail.com> (Patrick Robb's message of "Tue, 3 Oct 2023 16:22:04 -0400")
Patrick Robb <probb@iol.unh.edu> writes:
> Thanks, this should help greatly going forward in the community lab.
>
> As it relates to our arm64 unit testing, I will give it a few days (or longer if needed) for next branches to rebase off of
> main and then re-enable arm64 unit testing with the eal_flags_file_prefix_autotest added to the skipped list. David
> explained to me on slack that this patch would not likely be a candidate for backporting, so of course LTS will be
> excluded.
This is in testing area, and maybe it can be considered as an exception
if it allows for improved LTS testing. CC'd Kevin.
next prev parent reply other threads:[~2023-10-04 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 10:58 [RFC PATCH] " Bruce Richardson
2023-08-29 9:34 ` Thomas Monjalon
2023-08-29 13:27 ` Aaron Conole
2023-08-29 13:39 ` Bruce Richardson
2023-08-31 10:06 ` [PATCH v2] " Bruce Richardson
2023-08-31 10:18 ` [PATCH v3] " Bruce Richardson
2023-08-31 13:58 ` Bruce Richardson
2023-09-14 15:16 ` [PATCH v4] " Bruce Richardson
2023-09-25 16:26 ` Aaron Conole
2023-10-02 9:20 ` David Marchand
2023-10-03 20:22 ` Patrick Robb
2023-10-04 15:13 ` Aaron Conole [this message]
2023-10-09 20:03 ` Patrick Robb
2023-10-20 15:02 ` Patrick Robb
2023-10-20 15:08 ` Bruce Richardson
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=f7t4jj6h14i.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).