From: David Marchand <david.marchand@redhat.com>
To: "Huang, ChenyuX" <chenyux.huang@intel.com>,
"Gao, DaxueX" <daxuex.gao@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, Aaron Conole <aconole@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: Diagnosing CI Failures Question
Date: Tue, 21 Mar 2023 11:10:36 +0100 [thread overview]
Message-ID: <CAJFAV8wVEBmsHnevCOwYMZZ9y7vGc=SWqLhGO3t7ekB0CsgH6w@mail.gmail.com> (raw)
In-Reply-To: <20230317145950.GB29683@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
Hello guys,
On Fri, Mar 17, 2023 at 3:59 PM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
>
> On Fri, Mar 17, 2023 at 04:27:24AM +0000, Huang, ChenyuX wrote:
> > There is a problem with the ci machine and it has been repaired. No problem with the new report
>
> Is there a way to "re-run" existing patch sets through the
> ci/intel-Functional tests? or is the only way to re-submit the same
> series to dev@dpdk.org?
>
> Additionally, in the case of failures how do we extract artifacts for
> diagnosis? for large tree-wide changes it's quite difficult to rely
> entirely on code review to guess what caused a failure.
Can you reply to Tyler?
Thanks.
--
David Marchand
next prev parent reply other threads:[~2023-03-21 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316165126.GB8277@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
2023-03-16 16:59 ` David Marchand
2023-03-17 4:27 ` Huang, ChenyuX
2023-03-17 14:59 ` Tyler Retzlaff
2023-03-21 10:10 ` David Marchand [this message]
2023-03-22 1:02 ` Gao, DaxueX
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='CAJFAV8wVEBmsHnevCOwYMZZ9y7vGc=SWqLhGO3t7ekB0CsgH6w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=chenyux.huang@intel.com \
--cc=ci@dpdk.org \
--cc=daxuex.gao@intel.com \
--cc=john.mcnamara@intel.com \
--cc=roretzla@linux.microsoft.com \
--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).