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 48A0E45BA1; Tue, 22 Oct 2024 23:22:15 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 41E85402E9; Tue, 22 Oct 2024 23:22:15 +0200 (CEST) Received: from mail-qk1-f171.google.com (mail-qk1-f171.google.com [209.85.222.171]) by mails.dpdk.org (Postfix) with ESMTP id 9C8CE40151 for ; Tue, 22 Oct 2024 23:22:14 +0200 (CEST) Received: by mail-qk1-f171.google.com with SMTP id af79cd13be357-7b15d7b7a32so347772685a.1 for ; Tue, 22 Oct 2024 14:22:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1729632134; x=1730236934; darn=dpdk.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=xIOX8951IEwU79/NAMvcxXE86fYzGmWwWpEelEQ8LfQ=; b=INKvmcpfFWCe7dlnNH1rlyivQpSoLvJmW4IYDsaxyIdspHRc7m6j23oR0c1I564ZoR hwQcFuoImerkmodY/uQPtCMXcF3Uog8HxNY1oM5zkmA+IexKoIcpZVahdYEBYgVExRY3 yiEnvFlrdEsfFIToiL0SyoDP+Posut1XkKHak= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729632134; x=1730236934; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xIOX8951IEwU79/NAMvcxXE86fYzGmWwWpEelEQ8LfQ=; b=io6U3YlFBk5j9YIKBqtBjeugJ03wtEtS7a/1lXBRCi609kLmf1zCyLLCvTFCpYJCFl WuAN/25VPlpkaIZDzPvyvHxz4PsrU92yXDEOHfExlZM12RtgYnGAGdNERRsdpA5y7vgD 54H4jppt3DD7yjbtnSeFEy9wWJG9KASbkxSGQ0IQXKuF30QTmb2Fuo8Z43UInTs8haO1 cUd7lv6oHpHhZ+EYPDVlNFWM/kgcVDbvuAAOv8/a64qcJwknNKtkPLxsnBGdYFsFTyJe JYiJn8wuSEqZDmU98hP3ROnClQpq8FnWdJ6XcNWLESD5o325AosYdXUEP1N44n+5xt6W dbLQ== X-Gm-Message-State: AOJu0Yxrm5KLqSMrNT18wsOOfxEVpcMio/bZWQDxAnhd+rN6g5xhHEEO F6byGyGnKliZ1AVuicArTeI1AK1TejRF0bXHacD4Dkm89JyptWEeJnU54hDMnFA= X-Google-Smtp-Source: AGHT+IFFJpdkfzobAUJDJKpaWpwtMwG22GwrJ8aAm7V7ebggZa4CXSb9uKnR0roASYuOVIMV55UN/Q== X-Received: by 2002:a05:6214:2b87:b0:6cc:221:9049 with SMTP id 6a1803df08f44-6ce3414ece2mr5673826d6.15.1729632134073; Tue, 22 Oct 2024 14:22:14 -0700 (PDT) Received: from d121003.iol.unh.edu ([2606:4100:3880:1210::219]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6ce009e274bsm33121556d6.118.2024.10.22.14.22.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Oct 2024 14:22:13 -0700 (PDT) From: Patrick Robb To: thomas@monjalon.net Cc: web@dpdk.org, ahassick@iol.unh.edu, bruce.richardson@intel.com, aconole@redhat.com, zhoumin@loongson.cn, Patrick Robb Subject: [PATCH] web: adding section to explain recheck rebase option Date: Tue, 22 Oct 2024 17:20:48 -0400 Message-ID: <20241022212048.2433398-1-probb@iol.unh.edu> X-Mailer: git-send-email 2.46.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: web-bounces@dpdk.org The UNH-IOL Community Lab now supports an option to re-apply a patch series for a recheck request to a specific branch before starting the retests. This commit updates the dpdk testing page, adding an explanation of the rebase option and how it compares to the basic recheck function, and provides a new example usage for rebase. Signed-off-by: Patrick Robb --- content/testing/_index.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/content/testing/_index.md b/content/testing/_index.md index 7e17d97..31b464c 100644 --- a/content/testing/_index.md +++ b/content/testing/_index.md @@ -113,6 +113,8 @@ do not yet support this feature. If CI reports a failure for a test label on Patchwork, it is possible to request a retest of a patch or series on those label(s). +The default behavior is that your DPDK patch will be retested "as-is," +i.e. your series is not re-applied before testing. For a list of Patchwork testing labels, send an email reply on the patch or cover letter like so: ``` Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance, iol-unit-arm64-testing, github-robot @@ -120,8 +122,20 @@ Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance, iol-unit-a Note that you may omit any labels which are not failing. -This is currently supported by the UNH-IOL Community Lab, and the GitHub Actions robot, +You may also specify that your series must be re-applied to a given branch before running testing. +This is useful in a variety of situations, such as when +your patch originally got applied to a branch which was in a bad state, +or when the CI testing systems apply your patch to the wrong branch. + +In order to select the "re-apply" option, use the rebase={branch_name} option +when sending your recheck email. An example usage is provided below: +``` +Recheck-request: rebase=main, iol-intel-Functional, iol-intel-Performance +``` + +Rechecks are currently supported by the UNH-IOL Community Lab, and the GitHub Actions robot, so just those Patchwork testing labels beginning wih "iol-" or "github-robot". +IOL is the only lab supporting the re-apply (rebase) option. ### Mainline Monitoring -- 2.46.1