automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report]  |FAILURE| pw(77118) [v1, 2/2] net/ice: optimize Tx path on AVX512 vPMD
Date: 10 Sep 2020 02:27:59 -0700	[thread overview]
Message-ID: <fecc85$b8kaf7@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]


Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/77118

_apply issues_

Submitter: Leyi Rong <leyi.rong@intel.com>
Date: 2020-09-10 06:55:04
Reply_mail: 20200910065504.104217-3-leyi.rong@intel.com

DPDK git baseline:
	Repo:dpdk-next-net-intel, CommitID: 30507eead8b4e3e6b4e2b8491fb8263c758a8925
	Repo:dpdk, CommitID: a4235b781f5d7a7bda204f24a9d048696a2a484e


* Repo: dpdk-next-net-intel
Applying: net/ice: add AVX512 vector path
error: sha1 information is lacking or useless (drivers/net/ice/ice_rxtx.c).
error: could not build fake ancestor
Patch failed at 0001 net/ice: add AVX512 vector path
Use 'git am --show-current-patch' to see the failed patch
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".

* Repo: dpdk
Applying: net/ice: add AVX512 vector path
error: sha1 information is lacking or useless (drivers/net/ice/ice_rxtx.c).
error: could not build fake ancestor
Patch failed at 0001 net/ice: add AVX512 vector path
Use 'git am --show-current-patch' to see the failed patch
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".
DPDK STV team

                 reply	other threads:[~2020-09-10  9:28 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='fecc85$b8kaf7@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@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).