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 44C4EA0093 for ; Wed, 9 Mar 2022 15:49:06 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1794640687; Wed, 9 Mar 2022 15:49:06 +0100 (CET) Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) by mails.dpdk.org (Postfix) with ESMTP id 909C740395 for ; Wed, 9 Mar 2022 15:49:05 +0100 (CET) Received: by mail-io1-f50.google.com with SMTP id c23so2989353ioi.4 for ; Wed, 09 Mar 2022 06:49:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=rSQQ7y2Z8iAbxeGu88W5+msG41ccuBURE+cz+uQP4c0=; b=jU7kAEDY8bZqMthHjzOOFWYW4P82iCicQhQA3bMqVj4TvPc9Z7AC1+67McYFDaMhrv cyhS+Wlp0fVClXVNOdOvrZVnrfwo0wuzt7Huttg4GQ32APSMT3+wi8Z/dA4oi1x0fXAH Ylr1kqzBN8mlq/FbSf3aWdVEAkq4Hmq49NILI= 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=rSQQ7y2Z8iAbxeGu88W5+msG41ccuBURE+cz+uQP4c0=; b=AhYltZ6iUg716rTudREc8qRBJ0dxt1dEE1rV2KZq5BT+RcdyOX9MV3TCzblJWaIA+c hNJn7Xxka8AV9//otgcIs6CYx/1qwTeH11FL8He9+Bn8/WZh94x2kuPdh6En3gORzPdk GQEPvy0yBRWiy35AE3b7x+XyMWkmk9BMUByDg6XY0xyuwILJJOH2FNEwpzhzvy2nZloT V4PhGn6Sc0HHsI4bKq/bBDo6zplZVVliE9dlPKDGo9jTtArNrQM0GnwemWkfDcRsAf5z 0FbSMM6D2rlBUj7jFgvdcANBL5v4kL0o5pkZYAlF6vBkyZRVk3iEDqjOxV0Ogo9bh6bD ACqw== X-Gm-Message-State: AOAM530qAlGaXKskWMGdwICffH0/nXtUardfh2sm6A8eiMUe1oDvkYIK NvLxwv2FIdW0BaACFYl3F5dnfTgZbmqSuTEmjN4wmQ== X-Google-Smtp-Source: ABdhPJyI3nQBRbacgUEV1IDbpZxVLGM71yAFJUOWhicwHvcemJ3lq0GNrO4qnAR5Uy3chVQdBYqK7gvHSskxWL6BDzw= X-Received: by 2002:a05:6638:150c:b0:314:7784:e9c4 with SMTP id b12-20020a056638150c00b003147784e9c4mr20764103jat.163.1646837344899; Wed, 09 Mar 2022 06:49:04 -0800 (PST) MIME-Version: 1.0 References: <1928246.j4tpOohVRJ@thomas> In-Reply-To: From: Brandon Lo Date: Wed, 9 Mar 2022 09:48:29 -0500 Message-ID: Subject: Re: [dpdk-dev] [Bug 826] red_autotest random failures To: "Danilewicz, MarcinX" Cc: Lincoln Lavoie , "Dumitrescu, Cristian" , "Ajmera, Megha" , "Singh, Jasvinder" , "Zegota, AnnaX" , "Yigit, Ferruh" , "thomas@monjalon.net" , "david.marchand@redhat.com" , "ci@dpdk.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Wed, Mar 9, 2022 at 5:01 AM Danilewicz, MarcinX wrote: > > Hi Brandon, > > Sorry for late response, but I was busy in mean time. But after your mail= well .. I've tried to run test dpdk from docker image. Few instances of im= ages in parallel, enough to get machine fully loaded. But in turn, red_auto= test never failed. > > Is it possible for you to share some additional details? About hardware u= sed for testing, memory sizes, etc. To get some hint how to get these failu= res. I've seen other test failing constantly, depending on machine I was ru= nning other autotests. Maybe tests before red_autotest are changing hardwar= e to the state where red_autotest is failing. Anyone tried to change autote= sts execution order? Hi Marcin, Unfortunately, I don't have any more details other than the ones we talked about before. It is possible that the issue is not as common now that we limited the number of compile jobs that can happen on each machine at the same time. We limited the amount of RAM that each job can use again so that the systems are not getting a high load. > Also, I've don=E2=80=99t almost all to reproduce error and perhaps it is = better to ignore that random error for now. It looks like you are able to s= uccessfully pass that test all the time, even when is failing from time to = time. Right? If that is the true error, it will come out elsewhere. Yes, I think it's ok if you think the test is good for now. I haven't seen it fail in a while, so it might just be due to the load we put on the systems. If the issue comes up, I can contact you again. Thanks, Brandon -- Brandon Lo UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 blo@iol.unh.edu www.iol.unh.edu