From: Thomas Monjalon <firstname.lastname@example.org> To: email@example.com Cc: "O'Driscoll, Tim" <firstname.lastname@example.org> Subject: Re: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 21st Date: Tue, 21 May 2019 16:28:56 +0200 Message-ID: <5547763.pTxsDfsT3u@xps> (raw) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78BC5A0@IRSMSX108.ger.corp.intel.com> 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.
prev parent reply index Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-21 13:23 O'Driscoll, Tim 2019-05-21 13:27 ` Lincoln Lavoie 2019-05-21 14:28 ` Thomas Monjalon [this message]
Reply instructions: You may reply publically 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=5547763.pTxsDfsT3u@xps \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
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 \ firstname.lastname@example.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