DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Josh Soref <jsoref@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH 1/1] ci: restrict concurrency
Date: Thu, 13 Jan 2022 12:42:13 +0100	[thread overview]
Message-ID: <3172041.VqM8IeB0Os@thomas> (raw)
In-Reply-To: <20220112065019.58924-2-jsoref@gmail.com>

Hi,

The explanation should be in the patch, not the cover letter.
Actually, you don't need a cover letter for a single patch.
Copying it here:
"
dpdk is fairly expensive to build in GitHub.

It's helpful to abandon old builds as soon as there's a new
build waiting instead of wasting resources on the previous
round.
"

12/01/2022 07:50, Josh Soref:
> Signed-off-by: Josh Soref <jsoref@gmail.com>
> ---
> +    concurrency:
> +      group: build-${{ matrix.config.os }}-${{ matrix.config.compiler }}-${{ matrix.config.library }}-${{ matrix.config.cross }}-${{ matrix.config.mini }}-${{ github.event.pull_request.number || github.ref }}
> +      cancel-in-progress: true

The goal of the CI is to catch any issue in a submitted patch.
Is your change cancelling a test of a patch when another one is submitted?



  reply	other threads:[~2022-01-13 11:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  6:50 [PATCH 0/1] " Josh Soref
2022-01-12  6:50 ` [PATCH 1/1] " Josh Soref
2022-01-13 11:42   ` Thomas Monjalon [this message]
2022-01-13 12:41     ` Josh Soref
2022-02-02 14:17       ` Thomas Monjalon
2022-02-03 20:21         ` Aaron Conole
2022-02-03 21:44           ` Thomas Monjalon
2022-06-23  7:59             ` David Marchand

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=3172041.VqM8IeB0Os@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jsoref@gmail.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 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).