From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2AB17A04A3 for ; Tue, 16 Jun 2020 16:10:15 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1803F1BF84; Tue, 16 Jun 2020 16:10:15 +0200 (CEST) Received: from mail-il1-f174.google.com (mail-il1-f174.google.com [209.85.166.174]) by dpdk.org (Postfix) with ESMTP id F22101BF82 for ; Tue, 16 Jun 2020 16:10:12 +0200 (CEST) Received: by mail-il1-f174.google.com with SMTP id x18so1144367ilp.1 for ; Tue, 16 Jun 2020 07:10:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:from:date:message-id:subject:to; bh=oRplBU03TlqdiZHJsh3nhxXyiVV81B0F0K+Z0cFbEhg=; b=QGcn6ZbwGGSgGOlgGI4jAoJXeV/7zbyHXGtaL/Ccd0cNreD5SNFDJO/F2/jGqHVxJ4 XAQpDTXRniC5MOU+g1CxXggzpm3kLH3D+B4pNW6hNeKJUViPHCUvKChvuuaIBeC5Ufh1 Uji8SiSN3UTtoXn5zFYqGzxa5HeXa+DSkAJqI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=oRplBU03TlqdiZHJsh3nhxXyiVV81B0F0K+Z0cFbEhg=; b=POoPgZRJvc/qqFFpF1NtiK9QHOuFLZ0KzRVoo7DLMF6O0RQbCZamJh+HiVcQeiHoLz Or22oPvUaCL93BfmQtEeELbIP9TP78LTF5UpviJ/KM1sUksdFw4+l+zaE16PtHeR2UXO 4yz01TbZE7jnRgt7IrA3izxx3w8eszG1F/E0fWw0Vp0Yci2shWdniFxCnUuR+renGxoF bLMeUCE/fWXx7dxH7IGBxz5cJn2MVnuqhwcxoo5YMLOyy0sHZLNTTIsRgY6SBQxEuOML H/Y2QdfszIHPf0CXQsCr+fq+AleyL3G9BKixIVNizAFUe9+wHrM1EUBERDCbajIxGI9U yAWQ== X-Gm-Message-State: AOAM533pFKGqWbkt/KEkHYrCIuMxq52bC+XKkBdxmT3Q6G4itabxppeK z0U6kTn85UjAzNVuYjLmNXfPpEeTqsMs14XzU9K3Dtz7eOc2gg== X-Google-Smtp-Source: ABdhPJxBOhqKCSAl8iHjNgMNFHtUKr4e/2J2SFOJhzCSpCLxQ/yecTk4PXz8IPLX/Dxjy3EFCBOSynH+6n5Z5nFroCY= X-Received: by 2002:a05:6e02:13a9:: with SMTP id h9mr3293308ilo.20.1592316611958; Tue, 16 Jun 2020 07:10:11 -0700 (PDT) MIME-Version: 1.0 From: Brandon Lo Date: Tue, 16 Jun 2020 10:09:37 -0400 Message-ID: To: ci@dpdk.org Content-Type: multipart/alternative; boundary="00000000000006b3d305a8341a02" Subject: [dpdk-ci] Community CI Meeting Minutes - June 16, 2020 X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 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" --00000000000006b3d305a8341a02 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Attendees 1. Brandon Lo 2. Trishan de Lanerolle 3. James Hendergart 4. Juraj Linkes 5. Reyfone Wang 6. Tomasz Zawadzki 7. Owen Hilyard 8. Daniel Kirichok 9. David Liu 10. Thomas Monjalon 11. Lincoln Lavoie Agenda 1. CI Status 2. Test Development 3. Bugzilla Ticket Review 4. Any Other Business MinutesCI Status - Intel CI system updates - Need to invite the Intel CI team to the call - qian.q.xu@intel.com - john.mcnamara@intel.com - Travis CI - No updates - Community Lab - SPDK Build Failures - All 5 systems running SPDK compile testing fully functional. - SPDK Additional Unit Testing - Currently running on the Fedora VM in testing environment - Will be on by this Friday (probably sooner), after testing internally - Move to latest release branch to have more up-to-date commits during testing - Try it because of features that may make it easier to support - May need to fall back to LTS release branches if failures are occurring - Infrastructure Alert - System put in place to notify the team whenever an infrastructure failure occurs due to reliability issues - Broadcom Upgrade to include 100Gbe NICs - https://bugs.dpdk.org/show_bug.cgi?id=3D489 - Windows mingw-w64 compile testing (Bug-476) - Looking into setting this up and putting it onto the production dashboard - Other Build Services - Cirrus CI - Update on Redhat interns? - Expected on the 30th - OBS - Status of including package spec files in the main repos? - Not quite confident that we will do this - Only real motivation to have this is for OBS - Next steps - What=E2=80=99s missing: - =E2=80=9CJenkins=E2=80=9D job to run the pipeline - Something to monitor the result - Juraj to provide some of these quite soon(?) - Maybe submit a pull request to patchwork ci to see where it gets us. Test Development - Two systems that are working on getting development set up - Intel dev system with 2 servers - Occasionally borrowing Broadcom system from CI - Basic test cases working, but existing functional tests are not functioning properly - The tests that are passing are likely to be a false positive. - Questions - Is there a way to have TREX run and have a way to expose interfaces (some other way to make Scapy run) - Example on how to make Scapy run properly - Going through existing tests located within DTS - Some tests may be NIC specific; may need to work on scripts to improve coverage - Need to create a progress report in test development so that everybody in the group knows how much work has been done in the DTS team. - Brandon to lead recording the progress of the test development team. Bugzilla Ticket Review DPDK Community Lab Bug Tracker - New / Updated: - Bug 460 - Broadcom performance testing being setup - Testing fully functional. Reports being sent to patchworks under iol-broadcom-Performance - Bug 466 - Mellanox build errors occur randomly: - Stopping existing TREX processes before starting testing for Mellanox has stopped the failures for quite some time. Any Other Business - Emails submitted to patchwork through the mailing list with =E2=80=9Cwar= ning=E2=80=9D label are labeled as such due to failure of a submodule test. E.g.: SPDK build - Not marked as FAIL because of the lack of failures in the dpdk compile tests. - Next meeting: June 30, 2020 --=20 Brandon Lo UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 blo@iol.unh.edu www.iol.unh.edu --00000000000006b3d305a8341a02 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Attendees

    Brandon Lo

  1. Trishan de Lanero= lle

  2. James Hendergart

  3. Juraj Linkes

  4. Reyfone Wang<= /p>

  5. Tomasz Zawadzki

  6. Ow= en Hilyard

  7. Daniel Kirichok

    8. <= li dir=3D"ltr" style=3D"list-style-type:decimal;font-size:11pt;font-family:= Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:no= rmal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre= ">

    David Liu=C2=A0=C2=A0=C2=A0

  8. Thomas Monjalon

  9. Lincoln Lavoie

Agenda

  1. CI Status

  2. Test Development=C2=A0<= /span>

  3. Bugzilla Ticket Review

  4. Any Other Business

Minutes

CI Status

  • Intel CI sy= stem updates

  • Travis CI

    <= /li>

    • No upd= ates

  • Community Lab

    • SPDK Build Failures=

      • All 5 systems running SPDK compile testing fully functional.

        =

    • SPDK Additional Unit Testing

      • Currently running= on the Fedora VM in testing environment

      • Wil= l be on by this Friday (probably sooner), after testing internally

      • Move to latest release branch to have more up-to-dat= e commits during testing

        • Try it because of features that may make it easie= r to support

        • May need to fall back to LTS rele= ase branches if failures are occurring

    • Infrastructure Alert

      • System put in place to notify the team wheneve= r an infrastructure failure occurs due to reliability issues

    • Broadcom Upgrade to include 100Gbe NICs

    • Windows mingw-w64 compile te= sting (Bug-476)

      • Looking into setting this up and putting it onto the pro= duction dashboard

  • Other Build Servic= es

    • Cirrus CI

      • Update on Redhat interns?

      • Expected on the 30th

    • OBS

      <= /li>

      • Status= of including package spec files in the main repos?

      • Not quite confident that we will do this

        • Only real motivation to= have this is for OBS

      • Next steps=

        • What= =E2=80=99s missing:

          • =E2=80=9CJenkins=E2=80=9D job to run the pipeline

          • Something to monitor the result

            • Juraj to pr= ovide some of these quite soon(?)

            • Maybe subm= it a pull request to patchwork ci to see where it gets us.

              • <= /ul>

    Test Development

    • Two systems that are working on getti= ng development set up

      • Intel dev system with 2 servers

        • <= p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><= span style=3D"font-size:11pt;background-color:transparent;font-variant-nume= ric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-spa= ce:pre-wrap">Occasionally borrowing Broadcom system from CI

        =

    • Basic test cases working, but existing functional tests = are not functioning properly

      • The tests that are passing are likely to be= a false positive.

    • Questions

      • Is there = a way to have TREX run and have a way to expose interfaces (some other way = to make Scapy run)

      • Example on how to make Sc= apy run properly

    • Going through existing t= ests located within DTS

      • Some tests may be NIC specific; may need to work= on scripts to improve coverage

    • Need t= o create a progress report in test development so that everybody in the gro= up knows how much work has been done in the DTS team.

      • Brandon to lead re= cording the progress of the test development team.

      Bugz= illa Ticket Review

      DPDK Community Lab Bug Tracker

      • New / Updated:=C2=A0

        • Bug 460 - Broadcom performance testing being setup

          • Testing fully func= tional. Reports being sent to patchworks under iol-broadcom-Performance

        • Bug 466 - Mellanox build errors occur rand= omly:

          • Stopping existing TREX processes before starting testing for Mella= nox has stopped the failures for quite some time.

        =

      = Any Other Business

      • Emails submitted to patchwork through the mailing list with= =E2=80=9Cwarning=E2=80=9D label are labeled as such due to failure of a su= bmodule test. E.g.: SPDK build

        • Not marked as FAIL because of the lack of= failures in the dpdk compile tests.

      • Next= meeting: June 30, 2020


      --

      Brandon Lo

      UNH InterOperability Laborator= y

      21 Madbury Rd, Suite 100, Durham, NH 03824

      blo@iol.unh.edu

      www.iol.unh.edu

--00000000000006b3d305a8341a02--