[dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 21st

[dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 21st

[O'Driscoll, Tim]

OVS Tests:
- Tests are running on Intel machines. Mellanox setup is in progress.
- Tests are run whenever DPDK master is updated, not per patch set, because the tests take ~4 hours. Testing is against the DPDK latest branch in OVS.
- Test results are in the dashboard under the tarballs tab. Once the test setup is complete, we can look at how to make these more readable/more visible.
- At the moment, test results go to the DPDK patchwork mailing list. We need to look at how to include OVS maintainers in the distribution.

SPDK Tests:
- The SPDK team are interested in contributing tests, similar to OVS. This would allow them to identify any compatibility issues earlier, and would give us increased test coverage for DPDK.
- I'll connect the SPDK team with Jeremy and Lincoln to discuss further.

Misc:
- Jeremy is on vacation for the next 2.5 weeks. UNH will have coverage to deal with support issues.
- I'll cancel the next meeting.

Re: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 21st

[Lincoln Lavoie]

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

Hi All,

If issues come up while Jeremy is out, please email dpdklab@iol.unh.edu,
and this will reflect to our team, so things can be resolved as quickly as
possible.

Cheers,
Lincoln

On Tue, May 21, 2019 at 9:23 AM O'Driscoll, Tim <tim.odriscoll@intel.com>
wrote:

> OVS Tests:
> - Tests are running on Intel machines. Mellanox setup is in progress.
> - Tests are run whenever DPDK master is updated, not per patch set,
> because the tests take ~4 hours. Testing is against the DPDK latest branch
> in OVS.
> - Test results are in the dashboard under the tarballs tab. Once the test
> setup is complete, we can look at how to make these more readable/more
> visible.
> - At the moment, test results go to the DPDK patchwork mailing list. We
> need to look at how to include OVS maintainers in the distribution.
>
> SPDK Tests:
> - The SPDK team are interested in contributing tests, similar to OVS. This
> would allow them to identify any compatibility issues earlier, and would
> give us increased test coverage for DPDK.
> - I'll connect the SPDK team with Jeremy and Lincoln to discuss further.
>
> Misc:
> - Jeremy is on vacation for the next 2.5 weeks. UNH will have coverage to
> deal with support issues.
> - I'll cancel the next meeting.
>
>
>
>
>
>

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

Re: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 21st

[Thomas Monjalon]

21/05/2019 15:23, O'Driscoll, Tim:
> OVS Tests:
> - Tests are running on Intel machines. Mellanox setup is in progress.
> - Tests are run whenever DPDK master is updated, not per patch set, because the tests take ~4 hours.

It defeats the initial goal of avoiding breaks.
Why is it taking to long?
Can we have a shorter test?

> Testing is against the DPDK latest branch in OVS.
> - Test results are in the dashboard under the tarballs tab. Once the test setup is complete, we can look at how to make these more readable/more visible.

It would be more visible if test is per patchset, integrated in patchwork.

> - At the moment, test results go to the DPDK patchwork mailing list. We need to look at how to include OVS maintainers in the distribution.
> 
> SPDK Tests:
> - The SPDK team are interested in contributing tests, similar to OVS. This would allow them to identify any compatibility issues earlier, and would give us increased test coverage for DPDK.
> - I'll connect the SPDK team with Jeremy and Lincoln to discuss further.

Please ask them to prepare a short test.