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 7FACA41DB6 for ; Thu, 2 Mar 2023 19:49:56 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 640BA40E09; Thu, 2 Mar 2023 19:49:56 +0100 (CET) Received: from mail-oi1-f179.google.com (mail-oi1-f179.google.com [209.85.167.179]) by mails.dpdk.org (Postfix) with ESMTP id AD707400D6 for ; Thu, 2 Mar 2023 19:49:55 +0100 (CET) Received: by mail-oi1-f179.google.com with SMTP id bj30so8582469oib.6 for ; Thu, 02 Mar 2023 10:49:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1677782995; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=izxvJFNxMK+a/BhkJ4SL+7ohEW0NeBlwbc0Um5B+EWc=; b=FmAhTCYJR9CVObZK0iYINMgDSBqbmSGg93d74hSoaFRb12dXki8RyFIbS5VicTCbGl Na3NF7szHuddbTKxBNBL3p4YTyOW/la4y1JnGEnH2UDRuwI3Qbmr7ymwwB3S/ZgBOIDn p2w3NfvBFCSU9bpHGqhWvmJn193OxQwefZxFw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677782995; 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=izxvJFNxMK+a/BhkJ4SL+7ohEW0NeBlwbc0Um5B+EWc=; b=w2x7+RH7tl3zSteegEFyHUpD6IEb8nruRimQA0zbsgA61KVbWJB7kOGqFRt8FJ9Nn0 gctrm9Pd9iy0tghbfHYZaa5RivCKtepXRDMqsfSnBpC6IJq2cFw+El2vUhgHfXfS8Hvn jinogf3dGcoQK7Fqcl5xG7C73sPRAmbJMfVTr4eNXK4HCFa1A/BhICBjxUL+Da3m08Xe Cz11RI9vJCB1/i5JrNk0H5Ko9ibELYrDfkdWMukzANhGubqTIAaEAyn7swb3BDTJwjOZ PPCWdM8VGHAqdzkDave497akfI/GQ6SS3kNizSZa8dOxMav761JqQmmxlNJm+owfqe37 pKWA== X-Gm-Message-State: AO0yUKXxb7AZ/gLvAFQD6NuWBuEIEJwDUw7N1JYGAhJ/T6z+NrdsmflI WavtXxDUv7q3U0Mxk8/Jbe158ySbFRh49T+iAaon8A== X-Google-Smtp-Source: AK7set9biMNhuzzjMAHiNIs2Z1D66Sdy4XwBT7bnY58en+7iPLlTaKivtD1V4UpG0nHP2drlPGpIDLeBT+z+8YJlrxg= X-Received: by 2002:a05:6808:a98:b0:384:21e7:977c with SMTP id q24-20020a0568080a9800b0038421e7977cmr3292103oij.8.1677782994933; Thu, 02 Mar 2023 10:49:54 -0800 (PST) MIME-Version: 1.0 References: <08944dac-937f-5433-6ce5-fb6fbb2536ed@redhat.com> In-Reply-To: <08944dac-937f-5433-6ce5-fb6fbb2536ed@redhat.com> From: Patrick Robb Date: Thu, 2 Mar 2023 13:49:44 -0500 Message-ID: Subject: Re: UNH CI skipped tests To: Kevin Traynor Cc: Lincoln Lavoie , ci@dpdk.org, Aaron Conole , David Marchand , Jeremy Spewock Content-Type: multipart/alternative; boundary="0000000000006c739a05f5ef4b20" 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 --0000000000006c739a05f5ef4b20 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Kevin, The FIPS test has the same issue as the cryptodev tests - it cannot run on 21.11 due to a lacking dependency. We disabled the testing on the normal 21.11 branch but I missed 21.11-staging. Sorry about the oversight. All 3 tests are now disabled on 21.11-staging. The reason the two runs happened is that we were inadvertently polling DPDK-Stable AND our jenkinsfile repo for commits, and triggering new builds for commits to either repo. I have disabled polling to our Jenkinsfile repo, which should limit new builds to just commits to DPDK-Stable. Best, Patrick On Thu, Mar 2, 2023 at 9:04=E2=80=AFAM Kevin Traynor = wrote: > On 02/03/2023 13:22, Lincoln Lavoie wrote: > > 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 ma= ke > > sure those tests are excluded from future runs on the older > > staging branches. > > ok, cool, thanks. > > > > > In terms of the two runs, I'm not sure of the cause and we'll have to > look > > into that. > > > > No problem, it's not urgent or blocking. I will keep a closer eye on the > tests ran in future and just force a re-run if necessary. > > thanks, > Kevin. > > > 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 Patrick Robb Technical Service Manager UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 www.iol.unh.edu --0000000000006c739a05f5ef4b20 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Kevin,

The FIPS test has the same is= sue as the cryptodev tests - it cannot run on 21.11 due to a lacking depend= ency. We disabled the testing on the normal 21.11 branch but I missed 21.11= -staging. Sorry about the oversight. All 3 tests are now disabled on 21.11-= staging.=C2=A0

The reason the two runs happened is= that we were inadvertently polling DPDK-Stable AND our jenkinsfile repo fo= r commits, and triggering new builds for commits to either repo. I have dis= abled polling to our Jenkinsfile repo, which should limit new builds to jus= t commits to DPDK-Stable.=C2=A0

Best,
Pa= trick

On Thu, Mar 2, 2023 at 9:04=E2=80=AFAM Kevin Traynor <ktraynor@redhat.com> wrote:
On 02/03/2023 13:22, Lin= coln Lavoie wrote:
> Hi Kevin,
>
> The FIPS and crypto (ZUC / SNOW) testing shouldn't be running on t= he 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.=C2=A0 We= 'll make
> sure those tests are excluded from future runs on the older
> staging branches.

ok, cool, thanks.

>
> In terms of the two runs, I'm not sure of the cause and we'll = have to look
> into that.
>

No problem, it's not urgent or blocking. I will keep a closer eye on th= e
tests ran in future and just force a re-run if necessary.

thanks,
Kevin.

> Cheers,
> Lincoln
>
> On Thu, Mar 2, 2023 at 5:04=E2=80=AFAM Kevin Traynor <ktraynor@redhat.com> wro= te:
>
>> 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 ru= n
>> 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.io= l.unh.edu/results/dashboard/tarballs/23476/
>>
>> Second test run:
>> https://dpdkdashboard.io= l.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_autotes= t (fail)
>> NA NA (Linux container host) 10000 Mbps - cryptodev_sw_snow3g_auto= test
>> (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
>>
>>
>



--

Patrick Rob= b

Technical Service Manager

UNH InterOpera= bility Laboratory

21 Madbury Rd, Suite 100, Durham, NH 0= 3824

www.iol.unh.edu


--0000000000006c739a05f5ef4b20--