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 456CEA034F; Fri, 12 Nov 2021 15:15:54 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C71A1410E3; Fri, 12 Nov 2021 15:15:53 +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 525EE40692 for ; Fri, 12 Nov 2021 15:15:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1636726551; 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=gtu101iY5qv+ss1vY/Is7YuX25uSL1FMGdlFmlj8+FM=; b=KCxf95EkaQOsuRgbiYp5cxvc+YtyS7PwGT2pDBn7v2W1yqc+r86YIBU99O5J22hsrwwG5x 2fgor7EnXj1hI3v10PcJHQcq9GaB3RQxIsIg//W4C0RbVcBfqF4PibWWRWpWXemlz9XR2b 7tEQdpNGGg1eRef3jOqHygwjj2P7TO0= Received: from mail-lf1-f69.google.com (mail-lf1-f69.google.com [209.85.167.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-598-YFbj4fD8Nme3W_ko9VW75g-1; Fri, 12 Nov 2021 09:15:49 -0500 X-MC-Unique: YFbj4fD8Nme3W_ko9VW75g-1 Received: by mail-lf1-f69.google.com with SMTP id bq29-20020a056512151d00b003ffce2467adso3969484lfb.3 for ; Fri, 12 Nov 2021 06:15:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=gtu101iY5qv+ss1vY/Is7YuX25uSL1FMGdlFmlj8+FM=; b=yWAD1MBemEHbtMhgTkxBTbBqbKwnJIncoV59jzRlQL90FOd3jWvmRycgchiFBPa8UN h5SltP1qWKDZ4T1jZbtuN44OK+LBOhGFI5Oni/UZR2ZRx3p0xDMJ9XmpEZAopWxvPpje IT0kZckBAQ7dOyihVtZAgqkJZphd9CdzpF1rxBrwgHpX1aSby7pGFBZRyl8rbYn0Kmwi Efevg6h9Mx0mMGrvxRNXQ299MrB1A2tGkU9Wf6Ve/Tvy/t4TqTdUbxdblTKzcT7UFBqg DYDJQpv5c2wBwTUit6x1Ipx2AaqyXuPekAXDj+sw1IXUjJCrSuHdl4g//leBKwmcAgq9 wmEw== X-Gm-Message-State: AOAM53083zutzlXKDjycQ0A6+PP/Y/cI63fjZgOz5O2hL4cxdvKc/DL2 6SoSpy8QkjztjqXLFzHXjK0UoagwFvC4ERQ9xp5KMvp/PJM9QDRtaQUDk97JJswl0KtoDgp63OW 4fqQP7/bg+CgB6+fxr2o= X-Received: by 2002:ac2:5d68:: with SMTP id h8mr14123065lft.217.1636726547901; Fri, 12 Nov 2021 06:15:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJzKYjzN1VK17W3WJfWEV1gY4915Zh/JkFXytB9HQcKsccUuTggMuoYg7FdOpd6gItNt1LCXKMOqvO1Zbok9L+8= X-Received: by 2002:ac2:5d68:: with SMTP id h8mr14123031lft.217.1636726547632; Fri, 12 Nov 2021 06:15:47 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Fri, 12 Nov 2021 15:15:36 +0100 Message-ID: Subject: Re: [dpdk-dev] [Bug 826] red_autotest random failures To: Lincoln Lavoie Cc: Cristian Dumitrescu , dev , Aaron Conole , Thomas Monjalon , "Yigit, Ferruh" , ci@dpdk.org Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Fri, Nov 12, 2021 at 3:11 PM Lincoln Lavoie wrote= : >> This failure keeps on popping in the CI. >> The bug report is one month old, with no reply. >> >> >> I sent a proposal of removing red_autotest from the list executed by the= CI. >> https://patchwork.dpdk.org/project/dpdk/patch/20211027140458.2502-2-davi= d.marchand@redhat.com/ >> >> It might be the best solution waiting for an analysis. >> >> >> -- >> David Marchand >> > > Hi David, > > My understanding is, removing the test would require removing it from the= DPDK unit tests, we are just running the fast-tests suite for the unit tes= ts. DPDK's unit test structure / framework does not allow removing or cust= omizing the suite of tests beyond the suites. https://patchwork.dpdk.org/project/dpdk/patch/20211027140458.2502-2-david.m= archand@redhat.com/ > > In the lab, Brandon has been looking into and trying different configurat= ions for running the tests within the containers along the lines of the CPU= pinning requirements that might be assumed by the unit tests. So far, ever= ything he has tried has still had the similar failures / issues. We are st= ill looking into it, so the bug is not sitting without action, just no fina= l resolution. The mail I sent was not a comment for the investigation on UNH side. The ask is for Cristian to have a look too. --=20 David Marchand