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 A9C0041DC6 for ; Fri, 3 Mar 2023 10:59:24 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9DD48400D6; Fri, 3 Mar 2023 10:59:24 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 500DF400D6 for ; Fri, 3 Mar 2023 10:59:23 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1677837562; 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=jfyUTFKzc5dNrf0awACF2SQQF5Ms89RfWinGcb325Ls=; b=Z+AfaGpBbCRcCehFKqwAL1tHQ1xjZj7vguDSv1mrazAxVUyvI2jo4yOS4AP7uzc2WpUKWd vlbjUEEwcx1XNijbhC4e6+gjl8SwVQ3bvYtz0GjK+8kHRtMIAQImbpS2Ecw4/AbU3+Nl7l XuGe5fogDuGpcUamP1bc3TW3d4AIZtc= Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-292-vm6SVvyVP8ybgnJY7rRlpA-1; Fri, 03 Mar 2023 04:59:21 -0500 X-MC-Unique: vm6SVvyVP8ybgnJY7rRlpA-1 Received: by mail-wr1-f71.google.com with SMTP id m7-20020a056000008700b002c7047ea429so298123wrx.21 for ; Fri, 03 Mar 2023 01:59:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677837560; h=content-transfer-encoding:in-reply-to:subject:from:references:cc:to :content-language:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=jfyUTFKzc5dNrf0awACF2SQQF5Ms89RfWinGcb325Ls=; b=V7Mxw2W/u5llEDftZd1Si9092FCjkRM/SlZFDFIherqUcm5nABjOeMpmeiDGbWvQV7 8TinV1qDQ2915xbYAiqTxRJKDvb/z89/9fMN6Kpoib94fDJqbnITkDEdG7L8HCo/9pm4 lu+qS5xjFaTMCBGNbR3mfGINPc2ZDNGoTPvoNjKrnBqm8Ua+BjRjR2CVcS3sO232NtiT 966cM+1Q2QdDbtyA9HaYsGD5c7dDpWWlmjFrAgrxv00z/a5BzV0G4jhLW4UlmogfDHYg 69uy2SI/ZbsoV6Ho8iCUB4quYHfytcj6NMYwEk7jE/JwPCeubEyts4xVPrUOEKyShEpn pvuA== X-Gm-Message-State: AO0yUKVSqmNwG2TgLtojX9ECly5nx1Wz2OteDC142Lc0S/n3FRDL3iT8 FRRLX1pi1ZDQzdL4zBcuOFP+nl9oPkC1sMwq11WsGe1m0nvbF1Us505VRlyyrXv1L2WzjekpzeX 1Mw== X-Received: by 2002:a05:600c:4509:b0:3eb:399d:ab28 with SMTP id t9-20020a05600c450900b003eb399dab28mr1013325wmo.37.1677837560361; Fri, 03 Mar 2023 01:59:20 -0800 (PST) X-Google-Smtp-Source: AK7set8dLl19LS+53B5ANPrIVqz/Lh10kZwer4LwotbCER/ADCV/jmuaIzYgVycKGPm6dQxMAhVtJQ== X-Received: by 2002:a05:600c:4509:b0:3eb:399d:ab28 with SMTP id t9-20020a05600c450900b003eb399dab28mr1013306wmo.37.1677837560026; Fri, 03 Mar 2023 01:59:20 -0800 (PST) Received: from [192.168.0.36] ([78.16.250.81]) by smtp.gmail.com with ESMTPSA id a17-20020a056000101100b002c553e061fdsm1713227wrx.112.2023.03.03.01.59.18 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Mar 2023 01:59:19 -0800 (PST) Message-ID: <7c0fae6e-638a-a806-0029-b228c4956870@redhat.com> Date: Fri, 3 Mar 2023 09:59:18 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 To: Patrick Robb Cc: Lincoln Lavoie , ci@dpdk.org, Aaron Conole , David Marchand , Jeremy Spewock References: <08944dac-937f-5433-6ce5-fb6fbb2536ed@redhat.com> From: Kevin Traynor Subject: Re: UNH CI skipped tests In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 On 02/03/2023 18:49, Patrick Robb wrote: > Hi Kevin, > Hi Patrick, > 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. > Cool, thanks. > 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. > I'm not sure that was the reason for the second test run. I did that deliberately... - I ran the initial run on the original commit (pass) - I added a new dependency/build impacting commit and saw new tests and failures - I wanted to understand if the new tests and failures were related to the single commit allowing additional tests to run, so... - I force pushed back to the original commit for a second run on the original commit. There I also saw the new tests so was able to confirm it was unrelated to the new commit. Just a thought wrt Jenkins repo, I'm not sure how often it gets updated and modifies tests. If a Jenkins repo update triggers a run, then it will be the only delta from the previous build, so won't that make it easier to debug if there is some issue? Otherwise dpdk-stable and Jenkins updates will be first tested together, which may make it harder to debug failures. I will leave it to your more better judgement the best approach wrt triggering builds on jenkins updates. Either is fine with me. thanks, Kevin. > Best, > Patrick > > On Thu, Mar 2, 2023 at 9:04 AM 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 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 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 AM 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 >>>> >>>> >>> >> >> >