From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: ci@dpdk.org
Subject: [dpdk-ci] Community CI Meeting Minutes - May 19, 2020
Date: Wed, 20 May 2020 14:33:53 -0400 [thread overview]
Message-ID: <CAOE1vsMY1qPf3jstz51h1KTDgB_3w7dFkNcJC9tVUnXAPHsjuA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4692 bytes --]
Hello All,
Here are the minute minutes from yesterday's meeting.
Attendees
1.
Lincoln Lavoie
2.
Trishan de Lanerolle
3.
David Liu
4.
James Hendergart
5.
Thomas Monjalon
6.
Aaron Conole
7.
Ali Alnubani
8.
Brandon Lo
9.
Daniel Kirichok
10.
Jiraj Linkes
11.
Owen Hilyard
12.
Spencer Couture
13.
Timothy Carlin
14.
Tomasz Zawadzki
Agenda
1.
CI Status
2.
Test Development
3.
Bugzilla Ticket Review
4.
Any Other Business
MinutesCI Status
-
UNH-IOL hosted community lab
-
Ticket: 460 Broadcom Setup in the lab, working on solving an
integration issue with the DTS and automation
-
SPDK build failures - Compile failures, need to investigate to if
this is being caused by an issue with DPDK, or if there is an integration
issue
-
Graffin Dashboard Issue - No data is currently showing up in the
charts currently. Ali will create a bug to track this.
-
Travis CI
-
Support believes they have resolved the issue with disk-quotas, which
seemed to show up more often with multi-arch testing. We will need to
monitor this to keep an eye out for other failures.
-
Other build services
-
Cirrus CI - Aaron has done a little bit of investigation
-
Has a few more platforms available (FreeBSD and Windows)
-
Not sure about “running code” for unit testing.
-
Not as “easy” to use on the configuration file side.
-
Redhat interns may be able to take a stab at getting this setup,
Aaron needs to confirm approval (might take 1 month).
-
SUSE Open Build Service - may be allowed to use for unit testing
-
ARM is looking at possible integrating this into DPDK patchwork
-
Juraj Linkes is looking into it, seems like it could provide
similar results to Travis.
-
Package based (package for each build required)
-
Might allow for running unit testing as well, but need to confirm.
-
Will have some more information for feedback from the community by
the next meeting.
-
Github Actions
-
Not currently being investigated at this time. Could be used to
run test cases for pushes / merges to master, but may not
easily integrate
with per-patch tests (which aren’t pushed up to Github).
-
To compare on each of the above options:
-
Arch / OS types / coverage
-
Compile vs unit testing
-
Ability to report to patchworks and reporting format /
customization
-
Code coverage numbers or code line coverage
-
Portability (where tests are run)
-
Config difficulty
-
Support & troubleshooting
Test Development
-
The UNH-IOL development team is kicking off this week, to review and
expand the coverage of the DTS test coverage and deployment/usage in the
Community Lab.
-
The goal is to ensure all test cases are up to date, can be run on
multiple NICs, and architectures, ensuring coverage of at least 40% of the
feature list (http://doc.dpdk.org/guides/nics/features.html).
-
As test cases are created and vetted, they will be rolled into CI
testing on the bare-metal systems hosted in the lab.
-
Python version target for DTS, we’ll confirm with the DTS maintainer,
but planning to aim for the latest long term supported version, unless
there is a really good reason not to.
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=2663&order=priority%2Cchangeddate%20DESC&product=lab&query_format=advanced&resolution=---
-
New:
-
479: Fedora 32 / gcc 10 build testing
Any Other Business
-
Next Community CI Meeting: June 2, 2020
--
*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: 33747 bytes --]
reply other threads:[~2020-05-20 18:34 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=CAOE1vsMY1qPf3jstz51h1KTDgB_3w7dFkNcJC9tVUnXAPHsjuA@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).