DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: ci@dpdk.org
Subject: Re: [CI] Github Robot - Recheck support
Date: Wed, 20 Dec 2023 15:06:58 -0500	[thread overview]
Message-ID: <f7t8r5ok599.fsf@redhat.com> (raw)
In-Reply-To: <16202329.JCcGWNJJiE@thomas> (Thomas Monjalon's message of "Wed,  20 Dec 2023 16:08:39 +0100")

Thomas Monjalon <thomas@monjalon.net> writes:

> 14/12/2023 14:43, Aaron Conole:
>> 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
> Please update the web page to include this new capability:
> 	https://core.dpdk.org/testing/#requesting-a-patch-retest


      reply	other threads:[~2023-12-20 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 13:43 Aaron Conole
2023-12-20 15:08 ` Thomas Monjalon
2023-12-20 20:06   ` Aaron Conole [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=f7t8r5ok599.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=thomas@monjalon.net \


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