DPDK CI discussions
 help / color / mirror / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: ci@dpdk.org
Subject: [dpdk-ci] Question about performance test
Date: Fri, 4 Jan 2019 12:45:58 +0200	[thread overview]
Message-ID: <CAHLOa7TnitO=wrB69B3b8BEvrV_va1pXrAGwUe+0euioQy1PZQ@mail.gmail.com> (raw)

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

Hi,
I have a question about DPDK CI process and the tests done when a patch is
submitted to dpdk-dev mailing list.
In DPDK patch work I see these response messages from the DPDK CI for all
patches:

...
ci/intel-Performance-Testing success Performance Testing PASS
ci/mellanox-Performance-Testing success Performance Testing PASS
...

My question is (I hope and believe the info is available publicly) : which
tests are run in the ci, generating these messages?  is it done with IXIA
and DTS ? (DPDK test suite, https://doc.dpdk.org/dts/gsg/) ? are these
l2fwd/l3fwd performance tests? or more than that ? and on which
Intel/Mellanox nics ?  Are these merely performance tests, or also
functional tests ?

And BTW, I noticed that the CI runs a full performance cycle also for doc
patches (at least these messages are generated), which is a kind of
redundant (unless there is some filter which checks that if a patch only
affects modules under "doc", than such a cycle is not done but the messages
are still sent)

Regards,
Rami Rosen

[-- Attachment #2: Type: text/html, Size: 2628 bytes --]

             reply	other threads:[~2019-01-04 10:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 10:45 Rami Rosen [this message]
2019-01-04 14:44 ` Jeremy Plsek
2019-01-04 15:33   ` Rami Rosen
2019-01-04 15:34   ` Thomas Monjalon
2019-01-04 16:15     ` Jeremy Plsek
2019-01-04 16:19       ` Thomas Monjalon
2019-01-08  6:40   ` Rami Rosen
2019-01-08  7:06     ` Tu, Lijuan
2019-01-08  8:23       ` Rami Rosen

Reply instructions:

You may reply publicly 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='CAHLOa7TnitO=wrB69B3b8BEvrV_va1pXrAGwUe+0euioQy1PZQ@mail.gmail.com' \
    --to=ramirose@gmail.com \
    --cc=ci@dpdk.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).