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 C84AA427F6 for ; Tue, 21 Mar 2023 11:10:52 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A678F40A7F; Tue, 21 Mar 2023 11:10:52 +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 A73F440A7A for ; Tue, 21 Mar 2023 11:10:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1679393450; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=47rAKPY6IZw+g7ReUyoXj5qPpHCNgh3xWGhQd0hB2ho=; b=aP7zOp9GSS3CK69ZN8U/Q4WiGCmZyh1YxHRqtzGS1adW8oMW/74HML4I09JOJ+AdYVnMwV K0ancZbjJefJm0O5JTlHqcjb2sQFnpYyiNAee+MDxu4MGeRkqmEK0q5SAofr5MHNXkpQ8N /JQK614e8Bl8akonxH91eZxo90M7qfw= Received: from mail-pl1-f197.google.com (mail-pl1-f197.google.com [209.85.214.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-515-kQC2QZm6OJab6BieWBn_bA-1; Tue, 21 Mar 2023 06:10:49 -0400 X-MC-Unique: kQC2QZm6OJab6BieWBn_bA-1 Received: by mail-pl1-f197.google.com with SMTP id d2-20020a170902cec200b001a1e8390831so231340plg.5 for ; Tue, 21 Mar 2023 03:10:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679393448; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=47rAKPY6IZw+g7ReUyoXj5qPpHCNgh3xWGhQd0hB2ho=; b=nhhWFrirPQ46DCWauiSq7HOnlMJO4bVYjPF7kiTQ6q8VXV+Ghl+eGiyrquGb0nz2B0 cQCUr9Ld2GeIB4SiMpof0q6wSw/7LTU5qlWKHO5Z/BdS85R6iZ6L++qfxG9JLbN63Zzb yhNfHmYSrlojucfcEez7RCTj1W2xNLAJP1scI67ne6kTzomiUW73yOtMrDPYQXm5q4oa LZgAADGvabufqT/2dicjaDNvdfH2h7V7EqF3R55wuSap4kSwCfm+7NXlHYCKVeolvVlc vR70UeS0xCR5FupLrcwJvYkegFKHKcCRUe6knkh/8ugNSn7xOtvyG26vw92dIyoM3MK0 1Whg== X-Gm-Message-State: AO0yUKUPfrZK9SuLQHo6c6iN9PkFO4HUbT7pyfBdhelPnzDVkT98QpqW FwC0gqUteZeSxhRP16jiNvJjnc3vjeFss/RaYJEw4ZoWVH6h/RZztiC1fSqcWGWZ9iC6uKdUpPv dslikyJMYA8dkpNLP/Q== X-Received: by 2002:a05:6a00:2193:b0:624:5886:4b4b with SMTP id h19-20020a056a00219300b0062458864b4bmr878205pfi.5.1679393448284; Tue, 21 Mar 2023 03:10:48 -0700 (PDT) X-Google-Smtp-Source: AK7set/xUG9KVAKnmcP/2AtSNIQKyVcyZoe40pBD0LhAI/ZQVUMp7Ojq3bzN7TnYl13/UV3Fnuam/bcnBY1fFkYjsh0= X-Received: by 2002:a05:6a00:2193:b0:624:5886:4b4b with SMTP id h19-20020a056a00219300b0062458864b4bmr878202pfi.5.1679393447994; Tue, 21 Mar 2023 03:10:47 -0700 (PDT) MIME-Version: 1.0 References: <20230316165126.GB8277@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <20230317145950.GB29683@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> In-Reply-To: <20230317145950.GB29683@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> From: David Marchand Date: Tue, 21 Mar 2023 11:10:36 +0100 Message-ID: Subject: Re: Diagnosing CI Failures Question To: "Huang, ChenyuX" , "Gao, DaxueX" Cc: "ci@dpdk.org" , Aaron Conole , Thomas Monjalon , Tyler Retzlaff , "Mcnamara, John" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Hello guys, On Fri, Mar 17, 2023 at 3:59=E2=80=AFPM Tyler Retzlaff wrote: > > On Fri, Mar 17, 2023 at 04:27:24AM +0000, Huang, ChenyuX wrote: > > There is a problem with the ci machine and it has been repaired. No pro= blem with the new report > > Is there a way to "re-run" existing patch sets through the > ci/intel-Functional tests? or is the only way to re-submit the same > series to dev@dpdk.org? > > Additionally, in the case of failures how do we extract artifacts for > diagnosis? for large tree-wide changes it's quite difficult to rely > entirely on code review to guess what caused a failure. Can you reply to Tyler? Thanks. --=20 David Marchand