DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: ci@dpdk.org, dev@dpdk.org
Subject: [CI] Github Robot - Recheck support
Date: Thu, 14 Dec 2023 08:43:15 -0500	[thread overview]
Message-ID: <f7tedfooq6k.fsf@redhat.com> (raw)

Greetings DPDK Developers,

The UNH IOL, and the DPDK CI community at large, have developed a
mechanism to request a test recheck for failures.  This allows
patch authors or maintainers who suspect that a failing test is
really a byproduct of something unrelated (flaky test, network issue,
etc) to tell the various CI labs to restart their testing.

Each lab is responsible for turning on this feature.  The Github Actions
robot run by Red Hat now has learned to parse this format.  The test
name that the robot will key on is 'github-robot'.  So an example of
asking it for a recheck:

  Recheck-request: github-robot

Or if there are multiple labs:

  Recheck-request: iol-compile-amd64-testing, github-robot


Some important notes:

 1. The Github Actions robot does not currently parse cover-letter

 2. The Github Actions robot is currently only using the direct polling
    API for retrieving details - this limits it to only scanning more
    recent series.

 3. As with the UNH IOL implementation, we are looking into adding an
    option that will allow to re-apply to the current tip of tree.

 4. As with the UNH IOL look into adding a retest vetting process - if
    the current permissions become an issue.


             reply	other threads:[~2023-12-14 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 13:43 Aaron Conole [this message]
2023-12-20 15:08 ` Thomas Monjalon
2023-12-20 20:06   ` Aaron Conole

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=f7tedfooq6k.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \


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