DPDK CI discussions
 help / color / mirror / Atom feed
* [dpdk-ci] Community CI Meeting Minutes - January 14, 2021
@ 2021-01-14 16:12 Lincoln Lavoie
  2021-01-14 16:23 ` David Marchand
  0 siblings, 1 reply; 3+ messages in thread
From: Lincoln Lavoie @ 2021-01-14 16:12 UTC (permalink / raw)
  To: ci

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-ci] Community CI Meeting Minutes - January 14, 2021
  2021-01-14 16:12 [dpdk-ci] Community CI Meeting Minutes - January 14, 2021 Lincoln Lavoie
@ 2021-01-14 16:23 ` David Marchand
  2021-01-14 16:38   ` Aaron Conole
  0 siblings, 1 reply; 3+ messages in thread
From: David Marchand @ 2021-01-14 16:23 UTC (permalink / raw)
  To: Lincoln Lavoie; +Cc: ci

Sorry I did not attend.

On Thu, Jan 14, 2021 at 5:14 PM Lincoln Lavoie <lylavoie@iol.unh.edu> wrote:
> #################################################
> 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/

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 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.

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 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

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?


-- 
David Marchand


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-ci] Community CI Meeting Minutes - January 14, 2021
  2021-01-14 16:23 ` David Marchand
@ 2021-01-14 16:38   ` Aaron Conole
  0 siblings, 0 replies; 3+ messages in thread
From: Aaron Conole @ 2021-01-14 16:38 UTC (permalink / raw)
  To: David Marchand; +Cc: Lincoln Lavoie, ci

David Marchand <david.marchand@redhat.com> writes:

> Sorry I did not attend.
>
> On Thu, Jan 14, 2021 at 5:14 PM Lincoln Lavoie <lylavoie@iol.unh.edu> wrote:
>> #################################################
>> 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/
>
> 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
>> 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.
>
> I am not sure we will have enough credits, but ok, why not.

If it turns out that we can't get builds from it, we can just remove it.

>
>> * 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
>
> 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?


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-01-14 16:38 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-14 16:12 [dpdk-ci] Community CI Meeting Minutes - January 14, 2021 Lincoln Lavoie
2021-01-14 16:23 ` David Marchand
2021-01-14 16:38   ` Aaron Conole

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git