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 5394241DB5 for ; Thu, 2 Mar 2023 14:22:17 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3071A40E2D; Thu, 2 Mar 2023 14:22:17 +0100 (CET) Received: from mail-yw1-f182.google.com (mail-yw1-f182.google.com [209.85.128.182]) by mails.dpdk.org (Postfix) with ESMTP id 4BA0040E09 for ; Thu, 2 Mar 2023 14:22:16 +0100 (CET) Received: by mail-yw1-f182.google.com with SMTP id 00721157ae682-536bf92b55cso426230447b3.12 for ; Thu, 02 Mar 2023 05:22:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=luCH45qmS31+uMgPlK/LqW1afk0gI6ZYGqC52UCUOss=; b=ics6mSe2QY8yOSA/5bVRvkIr0BaLkz+h1j14eWRuI8DHLagGKRxSxSSOfO/Mfqm6wM Uec2sE4VGj8sQD+UblGUcyRDKh1oSSTnigtCEtGw8AM3eGhXSAnWBB0QHADE5qy1up9b 6KN36hS6ZOy97ULjzq7Wpg9XSsmfRLvLm8MKA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=luCH45qmS31+uMgPlK/LqW1afk0gI6ZYGqC52UCUOss=; b=4fKjBWvnbZSm6UNQmFbkCShTnuXZokzM/yLoIjQxvYNnicDiToF6hdMiNN6doO3FI+ IowiuGUkDzV+BW5Hv0s0DOGliBby523ig5zGHHzW1zi3NTQyzyzoiddPIcPOoviyoZTY ni+G2Q1at23/POU4mf0nAK2wfu0ueV033Q2e/F+XcSJuaFHn3WiAQpmAL4zq2ZQJJPpP q7SFk++4ehFeM+N5qCyBk2vu1BZOniGyo5ezkGgysD0ItTV4cMffs4vHrt2sWoM67ymV jjHHxZLgnutsfbSlE+zL6nHM17IaG9NKhvSZk8ktGH91CZ76jO972BDTkuTHtjLLzVz0 wcTQ== X-Gm-Message-State: AO0yUKVCUka0Z5+0Q1CA0N7MMdiLg2r9CZY5CX2p31v54v8zfJLJ3lEI aobeqEkQlZG21IjK8jag4Dn4vDdeS9MIDvnbQ+WXYQ== X-Google-Smtp-Source: AK7set9qi5mBku/QiZl0qpvq5CjORfkIaMfqVgtbkWVB7Hmvi1fHzJ+BTRFf8CDJPRjBu6ZN2kG/jyazPoH7Mro5JQo= X-Received: by 2002:a81:af08:0:b0:52e:e095:d840 with SMTP id n8-20020a81af08000000b0052ee095d840mr6117594ywh.0.1677763334625; Thu, 02 Mar 2023 05:22:14 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Lincoln Lavoie Date: Thu, 2 Mar 2023 08:22:03 -0500 Message-ID: Subject: Re: UNH CI skipped tests To: Kevin Traynor Cc: ci@dpdk.org, Aaron Conole , David Marchand , Patrick Robb , Jeremy Spewock Content-Type: multipart/alternative; boundary="00000000000093fd7905f5eab76d" 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 --00000000000093fd7905f5eab76d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Kevin, The FIPS and crypto (ZUC / SNOW) testing shouldn't be running on the older LTS branches, because they don't include the required patches that were released as part of 22.11. So, you can ignore those failures. We'll make sure those tests are excluded from future runs on the older staging branches. In terms of the two runs, I'm not sure of the cause and we'll have to look into that. Cheers, Lincoln On Thu, Mar 2, 2023 at 5:04=E2=80=AFAM Kevin Traynor = wrote: > Hi, > > I have a question about UNH CI periodic runs. I had 2x runs of CI on > 21.11-staging on the same commit, a few days apart. > > The issue I see is that the first test run came back all green, so I > assume good and I can push to 21.11 branch. However, the second run > comes back with additional tests that showed failures. > > So I'm wondering why there are additional tests in the second run? and > if/how skipped tests are being reported? > > At least with the fips tests I have seen previously so I don't think > they are all newly enabled tests in the days in-between. > > Details below. > > thanks, > Kevin. > > Initial test run: > https://dpdkdashboard.iol.unh.edu/results/dashboard/tarballs/23476/ > > Second test run: > https://dpdkdashboard.iol.unh.edu/results/dashboard/tarballs/23560/ > > Additional tests in the second run: > Ubuntu 20.04 VM - dpdk_fips_validation (warning, not reported in > dashboard?) > NA NA (Linux container host) 10000 Mbps - cryptodev_sw_zuc_autotest (fail= ) > NA NA (Linux container host) 10000 Mbps - cryptodev_sw_snow3g_autotest > (fail) > Arm Intel XL710-QDA2 4000 Mbps - lpm_autotest, unit_tests_mbuf > Arm Broadcom 25000 Mbps - unit_tests_mbuf,nic_single_core_tests > Ubuntu 20.04 ARM GCC Cross compile - dpdk_meson_compile > Ubuntu 20.04 ARM SVE - lpm_autotest > > --=20 *Lincoln Lavoie* Principal Engineer, Broadband Technologies 21 Madbury Rd., Ste. 100, Durham, NH 03824 lylavoie@iol.unh.edu https://www.iol.unh.edu +1-603-674-2755 (m) --00000000000093fd7905f5eab76d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi = Kevin,

The FIPS and crypt= o (ZUC / SNOW) testing=C2=A0shouldn't be running on the older LTS branc= hes, because they don't include the required patches that were released= =C2=A0as part of 22.11. So, you can ignore those failures.=C2=A0 We'll = make sure those tests are excluded from future runs on the older staging=C2= =A0branches.
In terms=C2= =A0of the two runs, I'm not sure of the cause and we'll have to loo= k into that.=C2=A0=C2=A0

= Cheers,
Lincoln

On Thu, Mar 2, 2023 at 5:04=E2=80=AFAM Kevin Trayno= r <ktraynor@redhat.com> wr= ote:
Hi,

I have a question about UNH CI periodic runs. I had 2x runs of CI on
21.11-staging on the same commit, a few days apart.

The issue I see is that the first test run came back all green, so I
assume good and I can push to 21.11 branch. However, the second run
comes back with additional tests that showed failures.

So I'm wondering why there are additional tests in the second run? and =
if/how skipped tests are being reported?

At least with the fips tests I have seen previously so I don't think they are all newly enabled tests in the days in-between.

Details below.

thanks,
Kevin.

Initial test run:
https://dpdkdashboard.iol.unh.edu= /results/dashboard/tarballs/23476/

Second test run:
https://dpdkdashboard.iol.unh.edu= /results/dashboard/tarballs/23560/

Additional tests in the second run:
Ubuntu 20.04 VM - dpdk_fips_validation (warning, not reported in dashboard?= )
NA NA (Linux container host) 10000 Mbps - cryptodev_sw_zuc_autotest (fail)<= br> NA NA (Linux container host) 10000 Mbps - cryptodev_sw_snow3g_autotest
(fail)
Arm Intel XL710-QDA2 4000 Mbps - lpm_autotest, unit_tests_mbuf
Arm Broadcom 25000 Mbps - unit_tests_mbuf,nic_single_core_tests
Ubuntu 20.04 ARM GCC Cross compile - dpdk_meson_compile
Ubuntu 20.04 ARM SVE - lpm_autotest



--
Lincoln Lavoie
Prin= cipal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, = Durham, NH 03824
+1-603-674-= 2755 (m)

<= /div>
--00000000000093fd7905f5eab76d--