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 DEEE2A0A02 for ; Thu, 14 Jan 2021 17:24:03 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B8480141398; Thu, 14 Jan 2021 17:24:03 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mails.dpdk.org (Postfix) with ESMTP id 00686141397 for ; Thu, 14 Jan 2021 17:24:01 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610641441; 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=MgvLG7vDzFxrJDqVZ4K3uiRpGcjr6d48NwKv4TkcyRo=; b=PeJE70iBT7P1Zx+1nnziYqninFue/cwsgNt9M03Q2Eq+zW+AKOWKTaTGvmdD+ATEEPPFJJ aIYS9GP6FXPs+s4VPRHwuIbiwTKlu1RyRaOjXGl+Bqrl8m6uEuz/wfwDyhri0rKgsNv/a3 1daldEYxSVxmcSVHIapqa8cjcVegUgQ= Received: from mail-vs1-f71.google.com (mail-vs1-f71.google.com [209.85.217.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-352-K_B2cnSqP92KpFbaHPGQMQ-1; Thu, 14 Jan 2021 11:23:58 -0500 X-MC-Unique: K_B2cnSqP92KpFbaHPGQMQ-1 Received: by mail-vs1-f71.google.com with SMTP id a18so956494vsp.9 for ; Thu, 14 Jan 2021 08:23:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=MgvLG7vDzFxrJDqVZ4K3uiRpGcjr6d48NwKv4TkcyRo=; b=cGD8nC+ciitXZoSaU0V3bJ+86t0ZYa3kz7y6Kfb6YwEnfP2Wc3Ja7qPwymTx74N9fe 2tlSJC2Prerlgs+t+zQ800Wzta89EQn1qEF+Xkqiel+WURcPb2NWGolYcGs94nN+N/yw /kiE53ssDAkQYFZF4Ry86N9o9w+uQsU95OG58CSnc0JQ+Pw07+Nt+kHK17V/3+uif+3L PUlQKoYF6NVc9US+cyWykI011ZjE+qDcEyeiC6FN47Lyfl8H9ed5hVWHh8wb14XV93I4 4Vd/IkE2PRAS+zn1SMEDsZ9dA9E9Kh6BVW3aibjKZqMIJhMGM5Ys+VZQwGTYUJQ5WGfP j7VQ== X-Gm-Message-State: AOAM530ru2xCfqJhIemPhNujqTcG4EqgfWDdGoyi05qSnb2LVNNP5fkH zBCipgEGMuybRFklh42LKEttbrdLbnXo+M5z54uJhc1EWKigNcklMUUw16qAC6/Omi/IVlm6mWs d8TT773ZoR7azAN5PlQ== X-Received: by 2002:a67:3093:: with SMTP id w141mr2225503vsw.27.1610641437452; Thu, 14 Jan 2021 08:23:57 -0800 (PST) X-Google-Smtp-Source: ABdhPJyiMUMq1XzWbCMUdPTf/C+op56eHTj4bTT/khJJK8B0GP3yRANPOR4PKFkocq69p57UXA0qH1mwJ9zNTE3IWdI= X-Received: by 2002:a67:3093:: with SMTP id w141mr2225480vsw.27.1610641437246; Thu, 14 Jan 2021 08:23:57 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Thu, 14 Jan 2021 17:23:45 +0100 Message-ID: To: Lincoln Lavoie Cc: 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 Subject: Re: [dpdk-ci] Community CI Meeting Minutes - January 14, 2021 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 Sender: "ci" Sorry I did not attend. On Thu, Jan 14, 2021 at 5:14 PM Lincoln Lavoie wrote= : > ################################################# > Minutes > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > CI Status > > ------------------------------------------------- > Intel Lab > > * Smoke tests are now enabled and results are being included in the repor= ts to patch works. Running about 6 test cases right now. Check the patchw= orks reports for the specific details (showing up as intel-test in pathwork= s as the label). Recommend to add a link to the DTS test plan into the rep= orts for each of the test cases that are being run. > * Merge coming for pmdinfogen, which will add some additional python depe= ndencies. Labs (UNH and Intel) will need to add these into the test system= s / DUTs where necessary: https://patches.dpdk.org/cover/81614/ Since it blocks those changes from being merged in the main repo, can we (Thomas or I) get a heads up when all systems are ready? > > ------------------------------------------------- > Github Actions / Travis CI / OBS > > * Github Actions have been running for about 1 month. Working on automat= ing the process of checking the output and posting the results to patchwork= s. ETA is probably about 1 to 2 weeks away. > * Planning to keep Travis CI around for now, specifically for the ARM bui= lds. Hopefully, the amount of =E2=80=9Cfree execution time=E2=80=9D will b= e enough to cover the ARM builds. I am not sure we will have enough credits, but ok, why not. > * OBS, still need a mechanism for timing out branches. This will get wor= ked on once the Github Action work is completed. Will take 2 to 4 weeks, o= nce started. > > ------------------------------------------------- > UNH-IOL Community Lab > > * We are aware of pending patchsets on the dashboard and will be investig= ating those today. > * Arm machines are now running compile and unit testing. > ** Now focusing on implementing functional and performance testing using = the NICs installed in the machine. > ** Broken unit test case: https://bugs.dpdk.org/show_bug.cgi?id=3D612 > * Mellanox systems are now running functional testing; we are currently m= onitoring these results for false negatives. We need to double check it se= nt an updated report to patchworks. > * Feature request: how could maintainer request rerun of jobs, possibly t= hrough the dashboard. > * Implemented a failure alert system to detect false failures quicker. > * Testing failures will now report the last 20 lines of log output, examp= le is here: http://mails.dpdk.org/archives/test-report/2021-January/174069.= html Thanks! I noticed today, it is a small improvement, but it will save us some time when looking at the reports. Just a comment on this example, we can only see the Ubuntu SPDK failure and not the other failures, is this expected? --=20 David Marchand