From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 630FF43722; Wed, 20 Dec 2023 21:07:03 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 472F640279; Wed, 20 Dec 2023 21:07:03 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id A476B40266 for ; Wed, 20 Dec 2023 21:07:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1703102821; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OoatEnLF8jgIWNGOqMfQVYAl2Ac/Rfpx7vmUw3uRtt8=; b=DJEsOn9RMGi5l6NXBY9tJID2mJvyL8jba1P0nyUUbxtgTCneeVF1+3By60Xl+28bOBc/ta sIOOFBnMdsGaGJvhp642TiwIov/Wtzx5evrkmc42NRloUqAlcpKRy41uIEaK7b0kd/Or1k bAXlZMM6TxtU/A2/NVR/w9Em7MqXgSw= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-311-u_z7VL1fO5CUUq5G9HcXhg-1; Wed, 20 Dec 2023 15:06:59 -0500 X-MC-Unique: u_z7VL1fO5CUUq5G9HcXhg-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 46A63807F71; Wed, 20 Dec 2023 20:06:59 +0000 (UTC) Received: from RHTPC1VM0NT (unknown [10.22.32.214]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0DA791C060AF; Wed, 20 Dec 2023 20:06:59 +0000 (UTC) From: Aaron Conole To: Thomas Monjalon Cc: ci@dpdk.org Subject: Re: [CI] Github Robot - Recheck support References: <16202329.JCcGWNJJiE@thomas> Date: Wed, 20 Dec 2023 15:06:58 -0500 In-Reply-To: <16202329.JCcGWNJJiE@thomas> (Thomas Monjalon's message of "Wed, 20 Dec 2023 16:08:39 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Thomas Monjalon 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 ACK