From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] Community CI Meeting Minutes
Date: Tue, 31 Aug 2021 17:47:45 +0200 [thread overview]
Message-ID: <3224374.3u8ESuPvME@thomas> (raw)
In-Reply-To: <CAOE1vsMJ5CX7dn9CY5ESAFMeV15zRLCvmJ6XkwjSvFXRzaRC8g@mail.gmail.com>
Then it should not be reported in patchwork.
Please let's not add more noise in patchwork.
26/08/2021 18:27, Lincoln Lavoie:
> This is specific to patches for DTS, where Intel doesn't have the
> infrastructure to run every possible test suite that is included in DTS.
> So, the warning is a notice to the submitter and the maintainer(s) the
> patch couldn't be tested. It's not really an issue related to the content
> of the patch itself (i.e. not about a breaking change or something like
> that).
>
> Cheers,
> Lincoln
>
> On Thu, Aug 26, 2021 at 12:05 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
>
> > 26/08/2021 15:33, Lincoln Lavoie:
> > > * For DTS CI, should authors be notified of skipped testing (i.e. CI
> > infrastructure doesn’t support that test suite)? Should this be marked as
> > a warning in patchwork? Agreed it should do both of these actions, notify
> > the author and mark the patch as warning in patchworks.
> >
> > Not sure to understand.
> > If a test is not supported, it is not an issue of the patch,
> > so why would it be reported in patchwork?
next prev parent reply other threads:[~2021-08-31 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 13:33 Lincoln Lavoie
2021-08-26 16:05 ` Thomas Monjalon
2021-08-26 16:27 ` Lincoln Lavoie
2021-08-31 15:47 ` Thomas Monjalon [this message]
2021-09-01 12:49 ` Owen Hilyard
2021-09-07 9:23 ` Thomas Monjalon
2021-09-07 8:36 ` David Marchand
2021-09-07 12:31 ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
-- strict thread matches above, loose matches on Subject: below --
2021-07-15 19:48 [dpdk-ci] " Lincoln Lavoie
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=3224374.3u8ESuPvME@thomas \
--to=thomas@monjalon.net \
--cc=ci@dpdk.org \
--cc=lylavoie@iol.unh.edu \
/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).