From: "Jiang, Cheng1" <cheng1.jiang@intel.com>
To: Aaron Conole <aconole@redhat.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, "Xia, Chenbo" <chenbo.xia@intel.com>,
"Hu, Jiayu" <jiayu.hu@intel.com>,
"Yang, YvonneX" <yvonnex.yang@intel.com>
Subject: Re: [dpdk-ci] CI work status check
Date: Fri, 15 Jan 2021 02:03:55 +0000 [thread overview]
Message-ID: <SJ0PR11MB5006557CF70CAFFD93CE8335DCA70@SJ0PR11MB5006.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f7tczy7zfyp.fsf@dhcp-25.97.bos.redhat.com>
Sure, thanks a lot.
> -----Original Message-----
> From: Aaron Conole <aconole@redhat.com>
> Sent: Thursday, January 14, 2021 11:38 PM
> To: Jiang, Cheng1 <cheng1.jiang@intel.com>
> Cc: ci@dpdk.org; Xia, Chenbo <chenbo.xia@intel.com>; Hu, Jiayu
> <jiayu.hu@intel.com>; Yang, YvonneX <yvonnex.yang@intel.com>
> Subject: Re: [dpdk-ci] CI work status check
>
> "Jiang, Cheng1" <cheng1.jiang@intel.com> writes:
>
> > Hi,
> >
> > Thanks a lot.
> > This patch set is based on dpdk-next-virtio tree. And it applied well in my
> environment.
> > It has passed some checks on the patchwork by the way. If it can't be
> > applied, then how could this happened? Really strange.
>
> I guess that's probably what happened here. The DPDK 0-day robot has
> difficulty right now to guess the right tree to apply against. Nothing 'wrong'
> here on your side. I will look at this closer and see if I can get it working
> better.
>
> >
> >> -----Original Message-----
> >> From: Aaron Conole <aconole@redhat.com>
> >> Sent: Wednesday, January 13, 2021 10:12 PM
> >> To: Jiang, Cheng1 <cheng1.jiang@intel.com>
> >> Cc: ci@dpdk.org; Xia, Chenbo <chenbo.xia@intel.com>
> >> Subject: Re: [dpdk-ci] CI work status check
> >>
> >> "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
prev parent reply other threads:[~2021-01-15 2:04 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
2021-01-14 2:23 ` Jiang, Cheng1
2021-01-14 15:38 ` Aaron Conole
2021-01-15 2:03 ` Jiang, Cheng1 [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=SJ0PR11MB5006557CF70CAFFD93CE8335DCA70@SJ0PR11MB5006.namprd11.prod.outlook.com \
--to=cheng1.jiang@intel.com \
--cc=aconole@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=ci@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=yvonnex.yang@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).