DPDK CI discussions
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] Minutes of DPDK Lab Meeting, October 9th
Date: Wed, 10 Oct 2018 06:49:14 +0000	[thread overview]
Message-ID: <VI1PR04MB4688AAFD1806588694E16EEB90E00@VI1PR04MB4688.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB7787AEE@IRSMSX107.ger.corp.intel.com>

Hello Tim,

Unfortunately, this meeting conflicts with my another meeting which recently started. So, at least for this month I won't be joining it.
I saw an item for me in this - inline comment below.

> -----Original Message-----
> From: ci <ci-bounces@dpdk.org> On Behalf Of O'Driscoll, Tim
> Sent: Tuesday, October 9, 2018 7:34 PM
> To: 'ci@dpdk.org' <ci@dpdk.org>
> Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, October 9th
> 
> 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.

My internal target was 29/Sep. But, resourcing issues caused this to be de-prioritize. I am planning for restarting work next week and hopefully closure before 20/Oct. (Hardware is already validated - we only need a couple of days for DTS validation. Thereafter, integration with UNH scripts would be coordinated).

-
Shreyansh

      reply	other threads:[~2018-10-10  6:49 UTC|newest]

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

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=VI1PR04MB4688AAFD1806588694E16EEB90E00@VI1PR04MB4688.eurprd04.prod.outlook.com \
    --to=shreyansh.jain@nxp.com \
    --cc=ci@dpdk.org \
    --cc=tim.odriscoll@intel.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
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).