From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>,
Aaron Conole <aconole@redhat.com>,
David Marchand <david.marchand@redhat.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thinh Tran <thinhtr@linux.vnet.ibm.com>,
Brandon Lo <blo@iol.unh.edu>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>, dev <dev@dpdk.org>,
"Yang, Qiming" <qiming.yang@intel.com>,
"ci@dpdk.org" <ci@dpdk.org>, dpdklab <dpdklab@iol.unh.edu>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>
Subject: Re: [dpdk-dev] [dpdk-ci] RHEL7 failures
Date: Tue, 12 Oct 2021 15:57:40 +0200 [thread overview]
Message-ID: <12868744.RCERaND3CH@thomas> (raw)
In-Reply-To: <2892d296-4690-ab6e-8c48-3e997644c2a6@intel.com>
12/10/2021 15:32, Ferruh Yigit:
> On 10/12/2021 1:39 PM, Lincoln Lavoie wrote:
> > Ferruh and Thinh,
> >
> > Yes, that will also work and should trigger the rebuild to the tip of the
> > current git repo / branch. Apologizes for forgetting that behavior is
> > built into the runner.
> >
> > All,
> >
> > That raises the question, for the planned work to allow triggering rebuilds
> > / reruns through patchwork, what is the expected behavior, rerun exactly
> > what was run before, or move to the current pointer (assuming it's moved
> > on) and build/run on top of that? What best aligns with everyone's
> > expectations, so we don't get confusion, etc.?
> >
>
> I don't see any problem to rerun the test with latest head of the repo,
> eventually patch on the patchwork needs to be merged on top of the latest
> head.
> Even the intention is only to test infrastructure etc with rerun,
> it shouldn't hurt to update the pointer too.
+1 to run on the latest HEAD
next prev parent reply other threads:[~2021-10-12 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 19:09 [dpdk-dev] RHEL7 failures Lincoln Lavoie
2021-10-05 21:46 ` Ferruh Yigit
2021-10-06 12:39 ` Lincoln Lavoie
2021-10-07 3:40 ` Zhang, Qi Z
2021-10-11 14:39 ` Thinh Tran
2021-10-11 14:42 ` Lincoln Lavoie
2021-10-11 16:39 ` Thinh Tran
2021-10-11 17:17 ` [dpdk-dev] [dpdk-ci] " Brandon Lo
2021-10-11 22:45 ` Thinh Tran
2021-10-12 0:57 ` Ferruh Yigit
2021-10-12 12:39 ` Lincoln Lavoie
2021-10-12 13:32 ` Ferruh Yigit
2021-10-12 13:57 ` Thomas Monjalon [this message]
2021-10-12 13:49 ` Thinh Tran
2021-10-12 13:50 ` Juraj Linkeš
2021-10-12 14:00 ` Thomas Monjalon
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=12868744.RCERaND3CH@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=aman.deep.singh@intel.com \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--cc=lylavoie@iol.unh.edu \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=thinhtr@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.