DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: [dpdk-ci] May 5, 2020 Community CI Meeting Minutes
Date: Tue, 5 May 2020 10:48:36 -0400	[thread overview]
Message-ID: <CAOE1vsOm+cC85J3pdR8TjOqDdjseKWa=396oUz86FzQ5Qx-jHw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4736 bytes --]

How to join the meetings

Next Meeting: TBD (will be announced on the ci@dpdk.org mailing list)

To join the Community CI meetings, please send an email to Trishan de
Lanerolle <tdelanerolle@linuxfoundation.org>.
May 5, 2020Attendees

   1.

   Lincoln Lavoie, UNH-IOL
   2.

   Bradon Lo, UNH-IOL
   3.

   David Liu, UNH-IOL
   4.

   Aaron Conole
   5.

   Cathal O’Hare
   6.

   Gal Cohen
   7.

   John McNamara
   8.

   Thomasz Zawadzki
   9.

   Trishan De Lanerolle
   10.

   Ali Alnubani
   11.

   Thomas Monjalon

Agenda

   1.

   Meeting Schedule & Logistics & Minutes
   2.

   CI Status
   3.

   Bugzilla Ticket Review
   4.

   Any other business

MinutesMeeting Schedule & Logistics & Minutes

   -

   Schedule & Duration
   -

      Keep to every other week schedule
      -

      Lincoln will confirm the time slot with James
      -

   Minutes
   -

      Need to finalize a location to keep minutes that is accessible to all
      participant
      -

      Minutes will be sent to the ci@dpdk.com mailing list, can put the
      -

      Add information for who to contact to join the meetings and get the
      calendar invite, etc.

CI Status

   -

   UNH hosted community lab
   -

      Patched false failures based on processor speed, instead of past run
      results
      -

      NXP has been contacted to keep an eye on false failures
      -

      Mellanox run failures being investigated, no common root cause
      determined yet
      -

         May be caused by TRex failures / linking with DPDK fork
         -

      Multiple emails for one context in patchworks has been fixed, and
      should prevent “last update” email from causing false pass or fail.
      -

      Still working with Broadcom, should be completed and online within
      the next two weeks.
      -

   Travis CI
   -

      Multi-arch support is a little buggy
      -

      Trishan will contact Travis CI to find out what would be gained from
      a paid account, and if they would eliminate the disk quota limitation
      -

   Other CI Tools
   -

      Cirrus CI - could provide support for Linux, BSD, and Window
      -

         Aaron will take a look at this, and report back what would
         required to begin using this for DPDK
         -

      Github Actions -
      -
         -

      SUSE Open Build Service - may be allowed to use for unit testing
      -

         ARM is looking at possible integrating this into DPDK patchwork
         -

   Other traffic generator tooling:
   -

      TRex forks DPDK, which should not be promoted.  Can we help encourage
      them to “not fork.”
      -

      Should other open source tools be tried, i.e. Warp-L7, these need to
      be supported into DTS to be used in the current performance lab.
      -

      Redhat may be able to help investigate this, based on the past
      developers being hired into Redhat

Bugzilla Ticket Review

https://bugs.dpdk.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&columnlist=product%2Ccomponent%2Cpriority%2Cbug_status%2Cassigned_to%2Cshort_desc%2Cchangeddate&component=job%20scripts&component=UNH%20infra&list_id=2592&order=priority&product=lab&query_format=advanced&resolution=---

Bug 425 - Eth Tests - Link Status Checks

   -

   Currently in code audit, to verify it’s not a duplicate

Bug 426 - Eth Tests - MTU Checks

   -

   Currently in code audit, to verify it’s not a duplicate

Bug 427 - Eth Tests - Promiscuous Support

   -

   Currently debugging the implementation

Bug 451 - Split dpdk-ci and dpdklab-ci scripts

   -

   Being started this week, since other bugs have been cleared out on the
   infrastructure.

Bug 459  - Performance Tuning and Results Stability Issues on NXP test
environment

   -

   Being tracked, but we have not seen failures since the last meetings.
   Nothing has been changed on the systems since the past meeting.

Bug 428 - Eth Tests - Hardware Checksum Checks

   -

   Need to discuss this on the lists, including the API maintainers
   -

   What is to be tested?

Bug 210 - Patches with dependency fails to apply

   -

   Brandon will give an estimate on difficulty to implement (i.e. time),
   may change the priority based on this outcome.

Any other business

   -

   None


-- 
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu/>

[-- Attachment #2: Type: text/html, Size: 37254 bytes --]

                 reply	other threads:[~2020-05-05 14:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOE1vsOm+cC85J3pdR8TjOqDdjseKWa=396oUz86FzQ5Qx-jHw@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --cc=ci@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).