* [dpdk-ci] Minutes of DPDK Lab Meeting, February 12
[not found] <9A3E4DCF947BAB4FBECB1FA88D4D67891F28183C@IRSMSX101.ger.corp.intel.com>
@ 2019-02-13 9:07 ` Ferruh Yigit
0 siblings, 0 replies; only message in thread
From: Ferruh Yigit @ 2019-02-13 9:07 UTC (permalink / raw)
To: 'ci@dpdk.org'
12 February 2019, DPDK Community lab meeting notes:
1. OvS testing
* Development effort continue on external (barrowed for two months)
Hardware.
* Need to resolve the additional HW requirement in _two months_.
* Do we need additional HW from vendors?
* It is an option to use same HW used for DPDK testing but can conflict
with DPDK testing configuration?
* OvS has priority of functionality and integration against performance
* Get feedback from vendors if they can provide additional HW?
* Aaron will/can provide NICs for OvS testing.
* OvS testing results will be integrated into dashboard
* AR: Jeremy will create a Bugzilla item to follow and document OvS effort.
* Current status, Setting up the new HW, it is expected to be up and running
end of this week.
* Next a few weeks work will be running the test cases, OvS Perf will be
running.
2. Community feedback on DTS
* Will continue with DTS for now, there is no poll data and won’t be a poll
* Wait OvS test case switch, how it run can give some idea like using other
consumers of DPDK for testing
* AR: Thomas will conduct 1:1 conversations about the issue and will continue
to collect feedback
3. Any feedback on Ali’s patch to identify correct sub-tree? Can we get Jeremy
to start using this for patches that don’t apply to master?
* No feedback on Bugzilla
* AR: Jeremy will try the script
4. Travis
* Latest version of travis patches has been sent to DPDK mail list by RedHat
* This is to integrate DPDK github repos to travis CI
* It may be better to have multiple CI to increase the coverage
5. Autotest
* Suggestion to add a new testcase to the DPDK community lab, which is unit
test autotest, predefined set of unit tests that can be run via single
command.
* AR: Ferruh will create a Bugzilla item for it.
6. Priority of the DPDK community lab, high to low:
* DPDK defects/issues (like sub-tree selection script)
* OvS Integration
* New testcases (like autotest)
7. Offline issues, following issues will be submitted as Bugzilla defect to
follow offline, AR: Ferruh
* Some “Not Applicable” items looks wrong
* https://lab.dpdk.org/results/dashboard/patchsets/4551/
* https://lab.dpdk.org/results/dashboard/patchsets/4546/
* A few more…
* Main tree is not up to date when patch sent, which cause merge error
* https://lab.dpdk.org/results/dashboard/patchsets/4534/
* Patches with dependency fails to apply
* https://lab.dpdk.org/results/dashboard/patchsets/4552/
* This is not exactly a defect but can be improved, will submit the
Bugzilla issue as a placeholder for improvement work
-----Original Appointment-----
*From:* O'Driscoll, Tim
*Sent:* Friday, June 15, 2018 11:06 AM
*To:* O'Driscoll, Tim; Yigit, Ferruh; 'Bob Noseworthy'; Mcnamara, John; 'Shepard
Siegel'; 'Thomas Monjalon'; 'Erez Scop'; 'Shreyansh Jain'; Xu, Qian Q;
'pmacarth@iol.unh.edu'; 'Matt Spencer'; Gema Gomez; 'George Zhao'; Mishra,
Shishir; 'Lixuming'; Tkachuk, Georgii; 'Trishan de Lanerolle'; Sean Campbell;
Ali Alnubani; 'May Chen'; Lodha, Nishant; Zhang, Chun
*Subject:* FW: DPDK Lab
*When:* Tuesday, February 12, 2019 2:00 PM-2:30 PM (UTC+00:00) Dublin,
Edinburgh, Lisbon, London.
*Where:* Skype Meeting
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-02-13 9:07 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <9A3E4DCF947BAB4FBECB1FA88D4D67891F28183C@IRSMSX101.ger.corp.intel.com>
2019-02-13 9:07 ` [dpdk-ci] Minutes of DPDK Lab Meeting, February 12 Ferruh Yigit
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).