DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: [dpdk-ci] Community CI Meeting Minutes - January 14, 2021
Date: Thu, 14 Jan 2021 11:12:09 -0500	[thread overview]
Message-ID: <CAOE1vsMDQsH6m2yVGpAwReBtndZmcYaruW06X=JNVwKTHj4TWg@mail.gmail.com> (raw)

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

Hello All,

Minutes from our meeting today.

January 14, 2021

#################################################
Attendees

1. Lincoln Lavoie
2. Owen Hilyard
3. David Liu
4. Shepard Siegel
5. Brandon Lo
6. Aaron Conole
7. Trishan de Lanerolle
8. Zhaoyan Chen
9. Lijuan Tu
10. Ali Alnubani
11. Michael Santana
12. Thomas Monjalon
13. Bruce Richardson
14. Tomasz Zawadzki
15. Dial-in: 17813082169


#################################################
Agenda

1. CI Status
2. Bugzilla Status
3. Test Development
4. Any other business

#################################################
Minutes

=================================================
CI Status

-------------------------------------------------
Intel Lab

* Smoke tests are now enabled and results are being included in the reports
to patch works.  Running about 6 test cases right now.  Check the
patchworks reports for the specific details (showing up as intel-test in
pathworks as the label).  Recommend to add a link to the DTS test plan into
the reports for each of the test cases that are being run.
* Merge coming for pmdinfogen, which will add some additional python
dependencies.  Labs (UNH and Intel) will need to add these into the test
systems / DUTs where necessary: https://patches.dpdk.org/cover/81614/

-------------------------------------------------
Github Actions / Travis CI / OBS

* Github Actions have been running for about 1 month.  Working on
automating the process of checking the output and posting the results to
patchworks.  ETA is probably about 1 to 2 weeks away.
* Planning to keep Travis CI around for now, specifically for the ARM
builds.  Hopefully, the amount of “free execution time” will be enough to
cover the ARM builds.
* OBS, still need a mechanism for timing out branches.  This will get
worked on once the Github Action work is completed.  Will take 2 to 4
weeks, once started.

-------------------------------------------------
UNH-IOL Community Lab

* We are aware of pending patchsets on the dashboard and will be
investigating 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=612
* Mellanox systems are now running functional testing; we are currently
monitoring these results for false negatives.  We need to double check it
sent an updated report to patchworks.
* Feature request: how could maintainer request rerun of jobs, possibly
through the dashboard.
* Implemented a failure alert system to detect false failures quicker.
* Testing failures will now report the last 20 lines of log output, example
is here: http://mails.dpdk.org/archives/test-report/2021-January/174069.html
* Patch for BUG-511 to categorize patches, to allow testing only applicable
components, (i.e. code was a driver change vs a core change).
https://mails.dpdk.org/archives/ci/2020-December/000902.html  Needs to be
reviewed and merged into dpdk-ci.

=================================================
Bugzilla Status

*
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&component=Intel%20Lab&component=Travis%20CI&list_id=3419&order=priority%2Cchangeddate%20DESC&product=lab&query_format=advanced&resolution=---

=================================================
Test Development

* Techboard is still working on developing priorities for 2021.

=================================================
Any other business

* Next Meeting: January 28, 2021

-- 
*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: 5924 bytes --]

             reply	other threads:[~2021-01-14 16:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 16:12 Lincoln Lavoie [this message]
2021-01-14 16:23 ` David Marchand
2021-01-14 16:38   ` Aaron Conole

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='CAOE1vsMDQsH6m2yVGpAwReBtndZmcYaruW06X=JNVwKTHj4TWg@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).