DPDK CI discussions
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "'ci@dpdk.org'" <ci@dpdk.org>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, September 25th
Date: Wed, 26 Sep 2018 21:04:39 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB776DC4F@IRSMSX107.ger.corp.intel.com> (raw)

Apply Errors in Dashboard:
- Jeremy has made a change to make the log visible.
- Causes of errors include build errors, genuine conflicts (e.g. KNI patches), patches which will apply on next-net but not on master.
- Docs directory is already excluded when applying patches, using the approach John suggested. Jeremy will check if there are any remaining documentation errors.
- To avoid sub-tree problem, we should be doing weekly merges of the sub-trees into master. This was already planned, but some issues have prevented it happening recently.
- Another approach to resolving the sub-tree problem is that if the apply fails, we merge the sub-trees into a new temporary master and try applying the patches again. Jeremy will look into this. Ferruh will provide any further info (which sub-trees to merge etc.) that's required.

Making Relative Performance Results Public:
- Before doing this, Erez asked for 1) comparison of patch performance versus the last GA release; 2) graphs of performance results.
- For 1), Jeremy will work on this. Pass/fail decision will still be made based on the comparison with master. The comparison to the last GA release will be added for reference.
- For 2), we agreed that graphs can be added later. We need to think about what specific data these should show and how they should be formatted.
- Erez will also check if any legal disclaimers are required by Mellanox.
- Ali will provide docs containing Mellanox config details.

New Hardware:
- UNH and NXP are working on setting up NXP hardware.

                 reply	other threads:[~2018-09-26 21:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=26FA93C7ED1EAA44AB77D62FBE1D27BAB776DC4F@IRSMSX107.ger.corp.intel.com \
    --to=tim.odriscoll@intel.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

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	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

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


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