DPDK CI discussions
 help / color / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jeremy Plsek <jplsek@iol.unh.edu>
Cc: ci@dpdk.org, Rami Rosen <ramirose@gmail.com>
Subject: Re: [dpdk-ci] Question about performance test
Date: Fri, 04 Jan 2019 16:34:03 +0100
Message-ID: <2631230.hnArF6gTu5@xps> (raw)
In-Reply-To: <CA+xUZB66fvJtTpqL=6U2gkZ2B6P6q60iNCKoZNq5WA7LYYm1dA@mail.gmail.com>

04/01/2019 15:44, Jeremy Plsek:
> Hi Rami,
> 
> I'm the current maintainer of the DPDK Performance CI. I realize that the
> performance results don't point to the website, so it's not obvious on
> where to find this information. You can find an overview of these tests
> here: https://lab.dpdk.org
> 
> Most of this information can be either found on the detailed results of a
> test (such as https://lab.dpdk.org/results/dashboard/patchsets/4157/) or on
> the about page (https://lab.dpdk.org/results/dashboard/about/).

Do you plan to add such URL in the report sent to patchwork?

> We don't apply the doc folder when applying the series, in case a patch
> included code unrelated to documentation. If others in the group feel that
> it's still unnecessary to include "doc" labeled series, I can look into
> filtering them out.

Instead of filtering based on the label, you could filter based on
the paths of modified files.
Note that such filter depends on the test you run,
because you could also test the doc syntax in the CI.

  parent reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 10:45 Rami Rosen
2019-01-04 14:44 ` Jeremy Plsek
2019-01-04 15:33   ` Rami Rosen
2019-01-04 15:34   ` Thomas Monjalon [this message]
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 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=2631230.hnArF6gTu5@xps \
    --to=thomas@monjalon.net \
    --cc=ci@dpdk.org \
    --cc=jplsek@iol.unh.edu \
    --cc=ramirose@gmail.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 \
		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