DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>,
	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>, "Aaron Conole" <aconole@redhat.com>,
	dpdklab <dpdklab@iol.unh.edu>,
	"Singh, Aman Deep" <aman.deep.singh@intel.com>,
	"David Marchand" <david.marchand@redhat.com>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: Re: [dpdk-ci] [dpdk-dev] RHEL7 failures
Date: Tue, 12 Oct 2021 16:00:10 +0200	[thread overview]
Message-ID: <3156763.r42A1DCDKm@thomas> (raw)
In-Reply-To: <9901ec83acf8460b9ed748d67121c05d@pantheon.tech>

12/10/2021 15:50, Juraj Linkeš:
> I'm used to Gerrit where reruns on a given version always run with the same parent commit. I think this makes sense since this would give us a way to rerun with the same parent and the latest parent (using a new upload). Also, the version we're trying to rerun may no longer apply to the current HEAD, so it makes sense from this point of view as well.

If a patch doesn't apply, it is good to trigger it in CI.
When sending a patch, the expectation is to apply to the latest HEAD,
without knowing exactly neither when it will be effectively applied,
nor when the CI will run any test.

PS: please do not top-post.

> Juraj
> From: ci <ci-bounces@dpdk.org> On Behalf Of Lincoln Lavoie
> 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.?
> Cheers,
> Lincoln

      reply	other threads:[~2021-10-12 14:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 19:09 [dpdk-ci] " Lincoln Lavoie
2021-10-05 21:46 ` [dpdk-ci] [dpdk-dev] " 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           ` 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
2021-10-12 13:49                   ` Thinh Tran
2021-10-12 13:50                   ` Juraj Linkeš
2021-10-12 14:00                     ` Thomas Monjalon [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3156763.r42A1DCDKm@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=juraj.linkes@pantheon.tech \
    --cc=lylavoie@iol.unh.edu \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=thinhtr@linux.vnet.ibm.com \


* 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).