DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: "Jiang\, Cheng1" <cheng1.jiang@intel.com>
Cc: "ci\@dpdk.org" <ci@dpdk.org>,  "Xia\, Chenbo" <chenbo.xia@intel.com>
Subject: Re: [dpdk-ci] CI work status check
Date: Wed, 13 Jan 2021 09:11:42 -0500	[thread overview]
Message-ID: <f7tft353p0h.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <SJ0PR11MB500635C2F5DEBE9CDA66F8B0DCA90@SJ0PR11MB5006.namprd11.prod.outlook.com> (Cheng1 Jiang's message of "Wed, 13 Jan 2021 08:26:59 +0000")

"Jiang, Cheng1" <cheng1.jiang@intel.com> writes:

> Hi,
>
>  
>
> I’m an engineer from DPDK project.
>
> I’ve sent a patch set to the community. And the ci check has not made any progress for more than a day, so I
> want to ask if there is a problem.

From the 0day robot, I see the following error:

  error: sha1 information is lacking or useless (examples/vhost/main.c).
  error: could not build fake ancestor
  hint: Use 'git am --show-current-patch' to see the failed patch
  Patch failed at 0001 examples/vhost: refactor vhost data path
  When you have resolved this problem, run "git am --continue".
  If you prefer to skip this patch, run "git am --skip" instead.
  To restore the original branch and stop patching, run "git am --abort".

So, looks like it didn't apply.  Which tree is this based on?

> Here is the link:
>
> http://patches.dpdk.org/patch/86366/
>
>  
>
> Looking forward to your reply.
>
> Thanks.
>
> Cheng


  reply	other threads:[~2021-01-13 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13  8:26 Jiang, Cheng1
2021-01-13 14:11 ` Aaron Conole [this message]
2021-01-14  2:23   ` Jiang, Cheng1
2021-01-14 15:38     ` Aaron Conole
2021-01-15  2:03       ` Jiang, Cheng1

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=f7tft353p0h.fsf@dhcp-25.97.bos.redhat.com \
    --to=aconole@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=cheng1.jiang@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).