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 605B4429E7; Tue, 25 Apr 2023 08:56:31 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E0CE540A7E; Tue, 25 Apr 2023 08:56:30 +0200 (CEST) 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 BA73D400D7 for ; Tue, 25 Apr 2023 08:56:29 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1682405789; 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=1VpMIyFsWph+tJ2t9Tl0TIr/PcGQC1LzuQPu4c0alT0=; b=a563P5Vgd04BAnBH86N8jdw1BZGBRHvIQw5WLIfHae6G+IYymkbtTAIY7/IZ/IX00ewhlx GYR/zOfm/ySelk3B0nEfPjL6B0LzEMK2wW8OkuOsJmo9DHpJstMXgSi4E8Vpk94oQX3xP1 PCY8xm7JF2qBFA718RQuctW4DM2Mb5w= Received: from mail-pg1-f200.google.com (mail-pg1-f200.google.com [209.85.215.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-107-OxHr-bfPO7y0G-XisURPCQ-1; Tue, 25 Apr 2023 02:56:27 -0400 X-MC-Unique: OxHr-bfPO7y0G-XisURPCQ-1 Received: by mail-pg1-f200.google.com with SMTP id 41be03b00d2f7-51b51394f32so3216392a12.1 for ; Mon, 24 Apr 2023 23:56:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682405787; x=1684997787; 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=1VpMIyFsWph+tJ2t9Tl0TIr/PcGQC1LzuQPu4c0alT0=; b=TD1ms/CxxSNEnU0qqVtbJUQljGfvrwlAK7un/9WK7a91biZNfKqAscaMYfqiv02kg7 fAauU/Wb7PtkspQZmk4U2wCgN1k66MVdTI2uzX10slISnoPG1x/Tt3fz8b2r2LUiccvs Lx7+bz4ZA5M5NOvphNc7rfsXuNpKC4hDSZZuM0yE2W/V+N0btFxiT+gLhFWI6gUd/buz 2iaFd5zJRTZqlBIvt/NTEXtsIItGdP7vJwB+P4hFsN865VTHZQ2uc4TRP1x1cju74miP FzwPuggr25840xryYa7V0jtyzXOuQG0IzEK+2I/oyPvnGGdaALAlGKmUGv39j9jDC/ha 4zFw== X-Gm-Message-State: AAQBX9e7EmJJklIvWL7yWcJbOHEycLFH3K5rOS8SIorPl5C6frdqUQA9 MmjDYLr147AURNwLAQZCVQeWodZwZIg5WpXLdUPq0Imks9QBdOx98642A/ky6sF4tSW2v9LHn4/ 3a+SDoEqnantX/7mtzeg= X-Received: by 2002:a05:6a20:4281:b0:f0:7ac1:ea61 with SMTP id o1-20020a056a20428100b000f07ac1ea61mr21393794pzj.6.1682405786954; Mon, 24 Apr 2023 23:56:26 -0700 (PDT) X-Google-Smtp-Source: AKy350as6LCKh0eWzJnhbpzB1JHXm8sWVs8QkI4rZNVoI35nN1t9zFW4EasHJZcn+k72CJTaluddvMI2E5fmgdrS1F4= X-Received: by 2002:a05:6a20:4281:b0:f0:7ac1:ea61 with SMTP id o1-20020a056a20428100b000f07ac1ea61mr21393771pzj.6.1682405786617; Mon, 24 Apr 2023 23:56:26 -0700 (PDT) MIME-Version: 1.0 References: <20230412181619.496342-1-joshwash@google.com> <20230421232022.342081-1-joshwash@google.com> In-Reply-To: From: David Marchand Date: Tue, 25 Apr 2023 08:56:15 +0200 Message-ID: Subject: Re: [PATCH v5] app/testpmd: txonly multiflow port change support To: Joshua Washington Cc: Aman Singh , Yuying Zhang , dev@dpdk.org, Rushil Gupta , dpdklab X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hello Joshua, On Mon, Apr 24, 2023 at 7:56=E2=80=AFPM Joshua Washington wrote: > > After updating the patch, it seems that the `lcores_autotest` unit test n= ow times out on Windows Server 2019. I looked at the test logs, but they we= re identical as far as I could tell, with the timed out test even printing = "Test OK" to stdout. Is this a flake? Or is there any other way to get extr= a information about why the test timed out or run the test with extra debug= ging information? In general, the UNH dashboard provides an archive with logs for each report, like for example: https://lab.dpdk.org/results/dashboard/patchsets/26090/ https://lab.dpdk.org/results/dashboard/results/results-uploads/test_runs/b5= a6a2743665426b937603587850aa6d/log_upload_file/2023/4/dpdk_5f34cc454df4_260= 90_2023-04-22_02-36-52_NA.zip This timeout is something I did not notice so far, Ccing UNH guys, for info= . Regarding your patch, the CI passes fine on the current main branch. And there is no relation between testpmd and the EAL unit tests. So this report is very likely a false positive. I triggered a retest on your patch. --=20 David Marchand