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, October 9th
Date: Tue, 9 Oct 2018 14:04:24 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB7787AEE@IRSMSX107.ger.corp.intel.com> (raw)

Apply Errors in Dashboard:
- Still seeing frequent apply errors in the dashboard.
- John's fix to exclude the docs directory doesn't seem to work. Perhaps Jeremy and John can follow up offline on this.
- Most errors seem to be caused by sub-trees being out of sync with master. Ferruh said that sub-trees should be merged by the end of this week ahead of RC1. We need to plan to keep sub-trees more in sync with master in future (weekly merge).
- Some apply errors are actually build errors. These are expected to fail. Jeremy will look into adding a separate status for build errors so that this is clear.

Other Dashboard Enhancements:
- Discussed priority of 1) adding graphs; 2) adding comparison versus last GA release. Agreed that we should do whichever is lowest effort first. Jeremy believes graphs are simpler to implement, so we'll focus on that first.

Making Relative Performance Results Public:
- Erez is working with Mellanox legal to determine what disclaimers need to be added.
- Ali is working on docs providing Mellanox config details.
- Also discussed the need for an explanation of the dashboard and the results for people looking at this for the first time. I'll work on a draft of this.

New Hardware:
- UNH and NXP are working on setting up NXP hardware.
- I'll check with Shreyansh to see if there's a target timeframe for getting this completed.

             reply	other threads:[~2018-10-09 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 14:04 O'Driscoll, Tim [this message]
2018-10-10  6:49 ` Shreyansh Jain

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=26FA93C7ED1EAA44AB77D62FBE1D27BAB7787AEE@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
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).