RE: Diagnosing CI Failures Question

["Gao, DaxueX" <daxuex.gao@intel.com>]

Hi Tyler,
Reruns can only be triggered by the ci manager, Submitting a new patch will automatically start testing.
Check for issues from a base branch, such as the dpdk branch, In the future, consider sending the ci/intel-Functional test results of the corresponding branch to the community to facilitate troubleshooting.

Daxue Gao

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: 2023年3月21日 18:11
> To: Huang, ChenyuX <chenyux.huang@intel.com>; Gao, DaxueX
> <daxuex.gao@intel.com>
> Cc: 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
> 
> 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