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 2EED141D3D for ; Thu, 2 Mar 2023 11:04:42 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2B21140EE7; Thu, 2 Mar 2023 11:04:42 +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 1D38040E09 for ; Thu, 2 Mar 2023 11:04:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1677751479; 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; bh=EI3+AVQRCMu9pE5eGAyU63QHLAxPU6kYeJjq+tETunE=; b=Ux9CLnWkuUQbKeV0eIPD5LnWmCjnOGE3bV5gJlHNe1QEKSCBEeaenGiJY0q7vqeZ8Zq+HV RHFn/PmO2ntK8Cqy1ISKA+sCJOfjNA/pK0vEF2XEJREN7LTGn7RsgvB8aJMCzvkOFgTuRP euC1MCxQcEdtZGgjQc30+F0muT0ehcg= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-449-VapR9e6tOiuybZtaTHL2Kg-1; Thu, 02 Mar 2023 05:04:38 -0500 X-MC-Unique: VapR9e6tOiuybZtaTHL2Kg-1 Received: by mail-wm1-f71.google.com with SMTP id k20-20020a05600c1c9400b003e2249bd2b4so5553190wms.5 for ; Thu, 02 Mar 2023 02:04:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1677751477; h=content-transfer-encoding:subject:cc:to:content-language:from :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=EI3+AVQRCMu9pE5eGAyU63QHLAxPU6kYeJjq+tETunE=; b=KT30fTXr+NoAlfUt7Z4Eq7wbiZ6NO7T5B5rXfjsKEtIC0CWCFw3R+Hu8k9MWTgeKB3 rk4QUKmuIc9jNfcZ0D0WVWaGTd6PIf3T2nVU82lpuYBTNwAFcBFjYtsbJbse/SN8Jax8 BYCdYxySRAcJVhC3XWdUW3ra5DXw27ZSZg+TPxTN7QpkGWtzhUjyJGMhzDBUG/CfngeX /6ugk7fSAsoWCvyxrp3vWj4MSvfG5bZV/ref+jJkv+RPAj8jaWRibHwxWjGJfxQRmW11 hF/CI1zbE1r8kN421RE/sHNt9kzPi27MVx7SNibLoaqh3R/1T5q6zAjxZuscei39dvLB c/Tw== X-Gm-Message-State: AO0yUKVfFSH6o30S6nmTBAq45dr0tghrLgGAz9ySjXlkDXmjQvr3MRVV qTHQxuSpoN7Sd4MKc6IJV7IXKaO01z8vne92oAMQY1VddWZhxSaM2+SjM3GO+/qYEEcKDvyMKiN J91hFOgLL12RV6HcmMDjTgfRCWZ7JivJZFRuCfvvZ6t4YZHRvsn4HZk0R45s= X-Received: by 2002:a05:600c:170a:b0:3eb:37ce:4c3d with SMTP id c10-20020a05600c170a00b003eb37ce4c3dmr3347647wmn.38.1677751477453; Thu, 02 Mar 2023 02:04:37 -0800 (PST) X-Google-Smtp-Source: AK7set+Ox/Bz/ISBGzvmCvKD5OCclDWm4gnYesmakHMLVLwI5RMXasETF9KfiXfc73pjB96FUGqmhw== X-Received: by 2002:a05:600c:170a:b0:3eb:37ce:4c3d with SMTP id c10-20020a05600c170a00b003eb37ce4c3dmr3347620wmn.38.1677751477102; Thu, 02 Mar 2023 02:04:37 -0800 (PST) Received: from [192.168.0.36] ([78.16.250.81]) by smtp.gmail.com with ESMTPSA id r18-20020a05600c35d200b003e21f959453sm2530045wmq.32.2023.03.02.02.04.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 02 Mar 2023 02:04:36 -0800 (PST) Message-ID: Date: Thu, 2 Mar 2023 10:04:35 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 From: Kevin Traynor To: ci@dpdk.org, Lincoln Lavoie , Owen Hilyard Cc: Aaron Conole , David Marchand Subject: UNH CI skipped tests 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: 7bit 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 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