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 80E0D41DB5 for ; Thu, 2 Mar 2023 15:04:40 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 65A60400D6; Thu, 2 Mar 2023 15:04:40 +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 F0E58400D6 for ; Thu, 2 Mar 2023 15:04:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1677765878; 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=6sLOOQlHJJFIqm/nthpC+kxjFxE20GUEUiRN7cFU6CE=; b=Cb4fsqhwbzCaISKlhB6J/JOsWK15LQpXbfbsRKkilEI8CKOxT/qDVUNIUmgyz+oqS2cSDJ +5ZDAsj0cDcMCiSS2v1wo1JiDQqBBpuNk4DhCaJcUo0S1muVnHORvz8zJaAOPcbI/soL/q osnLaRkCj//Rz8RJKn4cgoIzW3JDuak= 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-25-VdQ3MUseP3i-BLuWOSzKMg-1; Thu, 02 Mar 2023 09:04:35 -0500 X-MC-Unique: VdQ3MUseP3i-BLuWOSzKMg-1 Received: by mail-wr1-f71.google.com with SMTP id x3-20020a5d6503000000b002c8c421fdfaso3239071wru.15 for ; Thu, 02 Mar 2023 06:04:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677765873; 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=6sLOOQlHJJFIqm/nthpC+kxjFxE20GUEUiRN7cFU6CE=; b=IX3+SLX9opaTPsPmwQ7g1BU+RA1+ON9X9Nxy8ff/2BBsLTIyDcOtbljv//at+G6uTX hQYNVpZ2PXtIMB2MFFubhqMEUTPDQXG94kEY7gXZtZCtpltvXMxBxZVdjP62NL9+/0qb i9ZuzatbpBLZjyNDO6IV5OKXBSEjTrBKO3DCMrdj5SxRjtqQgMgmdGtwr2cywYUtyseC YJmDc0ik3IAfk/zRhriWkorDP5GBHb3khTImaQpCt6mjE2OmJnMqqyNYMr58jYfSxwyC LPQKrGKST/gUuZ6maaXNOmy2yb8grwkxkhSRZYyDr9waVdqTUqeNPpMOKgXV450o4OF/ Z+0A== X-Gm-Message-State: AO0yUKVgBzVNMtzX/T1uVIM6U2w0AbcXXZw/pompm2Bck2PVrzxQc77J XxjLwGOJE+nq3EIXFw95v3cOg8QaK3U3pd/H9n0rnLCvft7UeWd+95e9FKoJNdbWRd1tho+fQ+y h5Q== X-Received: by 2002:a05:600c:4929:b0:3ea:ea8a:a94a with SMTP id f41-20020a05600c492900b003eaea8aa94amr8280929wmp.27.1677765873562; Thu, 02 Mar 2023 06:04:33 -0800 (PST) X-Google-Smtp-Source: AK7set+VC5cp7GVr/mIyXN7NVcUJ2C0J2hv1kk7YayGz+UJUScow08vauD0i+UcbPkYduI8aLsht0w== X-Received: by 2002:a05:600c:4929:b0:3ea:ea8a:a94a with SMTP id f41-20020a05600c492900b003eaea8aa94amr8280903wmp.27.1677765873305; Thu, 02 Mar 2023 06:04:33 -0800 (PST) Received: from [192.168.0.36] ([78.16.250.81]) by smtp.gmail.com with ESMTPSA id v4-20020a5d6784000000b002425be3c9e2sm15473136wru.60.2023.03.02.06.04.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 02 Mar 2023 06:04:32 -0800 (PST) Message-ID: <08944dac-937f-5433-6ce5-fb6fbb2536ed@redhat.com> Date: Thu, 2 Mar 2023 14:04:31 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 To: Lincoln Lavoie Cc: ci@dpdk.org, Aaron Conole , David Marchand , Patrick Robb , Jeremy Spewock References: 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 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 >> >> >