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 C96D8436F0; Thu, 14 Dec 2023 14:43:19 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C43C0432BA; Thu, 14 Dec 2023 14:43:19 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id E97FA4327C for ; Thu, 14 Dec 2023 14:43:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1702561397; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=lxwnM/wH7qiExkS/G44DRt2v7TxtLJzywOHjjfdm+QM=; b=RBsHUYFEc37Ev03FLycdNliFcgdqmffCtLfocYHAOKvU2Z2H8fW76LZEQNAMtjwFpMue6x VTJigKFJI5mW0XpemIlJnbwtUh7hg2E2BHwfNU9Oqy6KtI5IWYIePam9WpTxp/zru9PNM4 EgAd/LruGNRmsS0efgXn10ZBvG2KW1g= 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-176-76oyZ7xdNLGHNHSWrAaTBw-1; Thu, 14 Dec 2023 08:43:16 -0500 X-MC-Unique: 76oyZ7xdNLGHNHSWrAaTBw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (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 C80FB85A58B; Thu, 14 Dec 2023 13:43:15 +0000 (UTC) Received: from RHTPC1VM0NT (unknown [10.22.32.214]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 95A513C25; Thu, 14 Dec 2023 13:43:15 +0000 (UTC) From: Aaron Conole To: ci@dpdk.org, dev@dpdk.org Subject: [CI] Github Robot - Recheck support Date: Thu, 14 Dec 2023 08:43:15 -0500 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.1 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 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 Etc. Some important notes: 1. The Github Actions robot does not currently parse cover-letter comments. 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. Thanks, Aaron