DPDK CI discussions
 help / color / mirror / Atom feed
From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: "'ci@dpdk.org'" <ci@dpdk.org>
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, Oct 23th
Date: Fri, 26 Oct 2018 04:36:25 +0000	[thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E3BCB69C5@shsmsx102.ccr.corp.intel.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]

Apply Errors in Dashboard:

1.      Ferruh has analyzed all the failures, see the attached excel for details. Went through all the failures one by one.

2.      DOC patches have been excluded. It should be fine in future.

3.      Wrong tree, Intel build would poll all the sub-trees and find one sub-tree can build, then build. It can work for build, but consider doing the performance test, so we will not

4.      Dependency to other patchset, this dependency is difficult to detect automatically since patchset has no strict format for the dependency patches. The solution is not urgent requested, and can be put aside.
MLX performance public status:
Erez got the confirmation about the disclaimers from legal and Ali is working on the configuration documents and targeted to send the link to Jeremy by end of this week.

Jeremy's update on dashboard: The graph to show the performance data is almost done. Jermey will send out the sample screenshot following the mail. Good progress. And next Jeremy will check the apply errors related CI.



[-- Attachment #1.2: Type: text/html, Size: 11617 bytes --]

[-- Attachment #2: lab anaylsis.xlsx --]
[-- Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet, Size: 11882 bytes --]

                 reply	other threads:[~2018-10-26  4:36 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=82F45D86ADE5454A95A89742C8D1410E3BCB69C5@shsmsx102.ccr.corp.intel.com \
    --to=qian.q.xu@intel.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).