DPDK CI discussions
 help / color / Atom feed
* [dpdk-ci] June 16, 2020 Community CI Meeting Minutes
@ 2020-07-01 17:20 Lincoln Lavoie
  0 siblings, 0 replies; only message in thread
From: Lincoln Lavoie @ 2020-07-01 17:20 UTC (permalink / raw)
  To: ci

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

June 16, 2020
Attendees
1. Brandon Lo
2. Trishan de Lanerolle
3. James Hendergart
4. Juraj Linkes
5. Reyfone Wang
6. Tomasz Zawadzki
7. Owen Hilyard
8. Daniel Kirichok
9. David Liu
10. Thomas Monjalon
11. Lincoln Lavoie
Agenda
1. CI Status
2. Test Development
3. Bugzilla Ticket Review
4. Any Other Business
Minutes
CI Status
* Intel CI system updates
   * Need to invite the Intel CI team to the call
      * qian.q.xu@intel.com
      * john.mcnamara@intel.com
* Travis CI
   * No updates
* Community Lab
   * SPDK Build Failures
      * All 5 systems running SPDK compile testing fully functional.
   * SPDK Additional Unit Testing
      * Currently running on the Fedora VM in testing environment
      * Will be on by this Friday (probably sooner), after testing
internally
      * Move to latest release branch to have more up-to-date commits
during testing
         * Try it because of features that may make it easier to support
         * May need to fall back to LTS release branches if failures are
occurring
   * Infrastructure Alert
      * System put in place to notify the team whenever an infrastructure
failure occurs due to reliability issues
   * Broadcom Upgrade to include 100Gbe NICs
      * https://bugs.dpdk.org/show_bug.cgi?id=489
   * Windows mingw-w64 compile testing (Bug-476)
      * Looking into setting this up and putting it onto the production
dashboard
* Other Build Services
   * Cirrus CI
      * Update on Redhat interns?
      * Expected on the 30th
   * OBS
      * Status of including package spec files in the main repos?
      * Not quite confident that we will do this
         * Only real motivation to have this is for OBS
      * Next steps
         * What’s missing:
            * “Jenkins” job to run the pipeline
            * Something to monitor the result
               * Juraj to provide some of these quite soon(?)
               * Maybe submit a pull request to patchwork ci to see where
it gets us.
Test Development
* Two systems that are working on getting development set up
   * Intel dev system with 2 servers
   * Occasionally borrowing Broadcom system from CI
* Basic test cases working, but existing functional tests are not
functioning properly
   * The tests that are passing are likely to be a false positive.
* Questions
   * Is there a way to have TREX run and have a way to expose interfaces
(some other way to make Scapy run)
   * Example on how to make Scapy run properly
* Going through existing tests located within DTS
   * Some tests may be NIC specific; may need to work on scripts to improve
coverage
* Need to create a progress report in test development so that everybody in
the group knows how much work has been done in the DTS team.
   * Brandon to lead recording the progress of the test development team.
Bugzilla Ticket Review
DPDK Community Lab Bug Tracker
* New / Updated:
   * Bug 460 - Broadcom performance testing being setup
      * Testing fully functional. Reports being sent to patchworks under
iol-broadcom-Performance
   * Bug 466 - Mellanox build errors occur randomly:
      * Stopping existing TREX processes before starting testing for
Mellanox has stopped the failures for quite some time.
Any Other Business
* Emails submitted to patchwork through the mailing list with “warning”
label are labeled as such due to failure of a submodule test. E.g.: SPDK
build
   * Not marked as FAIL because of the lack of failures in the dpdk compile
tests.
* Next meeting: June 30, 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: 4890 bytes --]

<div dir="ltr"><div class="gmail_default" style="font-size:small">June 16, 2020<br>Attendees<br>1. Brandon Lo<br>2. Trishan de Lanerolle<br>3. James Hendergart<br>4. Juraj Linkes<br>5. Reyfone Wang<br>6. Tomasz Zawadzki<br>7. Owen Hilyard<br>8. Daniel Kirichok<br>9. David Liu   <br>10. Thomas Monjalon<br>11. Lincoln Lavoie<br>Agenda<br>1. CI Status<br>2. Test Development <br>3. Bugzilla Ticket Review<br>4. Any Other Business<br>Minutes<br>CI Status<br>* Intel CI system updates<br>   * Need to invite the Intel CI team to the call<br>      * <a href="mailto:qian.q.xu@intel.com">qian.q.xu@intel.com</a><br>      * <a href="mailto:john.mcnamara@intel.com">john.mcnamara@intel.com</a> <br>* Travis CI<br>   * No updates<br>* Community Lab<br>   * SPDK Build Failures<br>      * All 5 systems running SPDK compile testing fully functional.<br>   * SPDK Additional Unit Testing<br>      * Currently running on the Fedora VM in testing environment<br>      * Will be on by this Friday (probably sooner), after testing internally<br>      * Move to latest release branch to have more up-to-date commits during testing<br>         * Try it because of features that may make it easier to support<br>         * May need to fall back to LTS release branches if failures are occurring<br>   * Infrastructure Alert<br>      * System put in place to notify the team whenever an infrastructure failure occurs due to reliability issues<br>   * Broadcom Upgrade to include 100Gbe NICs<br>      * <a href="https://bugs.dpdk.org/show_bug.cgi?id=489">https://bugs.dpdk.org/show_bug.cgi?id=489</a><br>   * Windows mingw-w64 compile testing (Bug-476)<br>      * Looking into setting this up and putting it onto the production dashboard<br>* Other Build Services<br>   * Cirrus CI<br>      * Update on Redhat interns?<br>      * Expected on the 30th<br>   * OBS<br>      * Status of including package spec files in the main repos?<br>      * Not quite confident that we will do this<br>         * Only real motivation to have this is for OBS<br>      * Next steps<br>         * What’s missing:<br>            * “Jenkins” job to run the pipeline<br>            * Something to monitor the result<br>               * Juraj to provide some of these quite soon(?)<br>               * Maybe submit a pull request to patchwork ci to see where it gets us.<br>Test Development<br>* Two systems that are working on getting development set up<br>   * Intel dev system with 2 servers<br>   * Occasionally borrowing Broadcom system from CI<br>* Basic test cases working, but existing functional tests are not functioning properly<br>   * The tests that are passing are likely to be a false positive.<br>* Questions<br>   * Is there a way to have TREX run and have a way to expose interfaces (some other way to make Scapy run)<br>   * Example on how to make Scapy run properly<br>* Going through existing tests located within DTS<br>   * Some tests may be NIC specific; may need to work on scripts to improve coverage<br>* Need to create a progress report in test development so that everybody in the group knows how much work has been done in the DTS team.<br>   * Brandon to lead recording the progress of the test development team.<br>Bugzilla Ticket Review<br>DPDK Community Lab Bug Tracker<br>* New / Updated: <br>   * Bug 460 - Broadcom performance testing being setup<br>      * Testing fully functional. Reports being sent to patchworks under iol-broadcom-Performance<br>   * Bug 466 - Mellanox build errors occur randomly:<br>      * Stopping existing TREX processes before starting testing for Mellanox has stopped the failures for quite some time.<br>Any Other Business<br>* Emails submitted to patchwork through the mailing list with “warning” label are labeled as such due to failure of a submodule test. E.g.: SPDK build<br>   * Not marked as FAIL because of the lack of failures in the dpdk compile tests.<br>* Next meeting: June 30, 2020<br></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b>Lincoln Lavoie</b><br></div><div>Senior Engineer, Broadband Technologies</div><div>21 Madbury Rd., Ste. 100, Durham, NH 03824</div><div><a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a></div><div><a href="https://www.iol.unh.edu" target="_blank">https://www.iol.unh.edu</a></div><div>+1-603-674-2755 (m)<br></div><div><a href="https://www.iol.unh.edu/" target="_blank"><img src="http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png"></a></div></div></div></div></div></div></div></div></div></div></div></div></div>

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-01 17:20 [dpdk-ci] June 16, 2020 Community CI Meeting Minutes Lincoln Lavoie

DPDK CI discussions

Archives are clonable:
	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


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


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