DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 190] Investigate some apply errors with unclear root cause
Date: Tue, 15 Jan 2019 14:53:06 +0000	[thread overview]
Message-ID: <bug-190-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=190

            Bug ID: 190
           Summary: Investigate some apply errors with unclear root cause
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: dashboard
          Assignee: ci@dpdk.org
          Reporter: ferruh.yigit@intel.com
                CC: jplsek@iol.unh.edu
  Target Milestone: ---

Hi Jeremey,

I have seen following apply errors while checking, not sure if that means any
error or not but creating this defect to analyze root cause if there is a fix
to address here:

1)
https://lab.dpdk.org/results/dashboard/patchsets/3766/
"
Checking patch test/test_distributor.c...
error: test/test_distributor.c: does not exist in index
Checking patch librte_distributor/rte_distributor.c...
error: librte_distributor/rte_distributor.c: does not exist in index
"

Both test/test_distributor.c & librte_distributor/rte_distributor.c should
exist, not sure about the error. Can it be any git repo synchronization issue?

2)
https://lab.dpdk.org/results/dashboard/patchsets/2190/
"
There are not yet any runs for this patch set or you do not have permission to
view detailed results for any test runs for this patch set.
"

Detail is missing for this one.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-01-15 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 14:53 bugzilla [this message]
2019-01-16 19:19 ` bugzilla
2019-01-16 19:19 ` bugzilla
2019-01-16 19:20 ` bugzilla

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=bug-190-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).