automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, Ivan.Malov@oktetlabs.ru
Subject: [dpdk-test-report] |WARNING| pw(101346) sid(19595) job(PER_PATCH_BUILD8705)[v4, 10/10] net/sfc: refine pattern of group flows in tunnel offload
Date: 13 Oct 2021 11:55:24 -0700	[thread overview]
Message-ID: <746b4b$ekqdss@orsmga008-auth.jf.intel.com> (raw)

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


Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/101346

_apply issues_

Submitter: Ivan Malov <Ivan.Malov@oktetlabs.ru>
Date: 2021-10-13 13:15:13
Reply_mail: 20211013131514.20376-11-ivan.malov@oktetlabs.ru

DPDK git baseline:
	Repo:dpdk-next-net, CommitID: bd026ee0e890eee3d63307c380ffefbf484055bd
	Repo:dpdk, CommitID: d75eed0fbe4b942bc6df2e2908a8b5c2c30c99aa


* Repo: dpdk-next-net
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: drivers/net/sfc/meson.build:90
error: drivers/net/sfc/meson.build: patch does not apply
error: patch failed: drivers/net/sfc/sfc_dp_rx.h:92
error: drivers/net/sfc/sfc_dp_rx.h: patch does not apply
error: patch failed: drivers/net/sfc/sfc_ef100_rx.c:20
error: drivers/net/sfc/sfc_ef100_rx.c: patch does not apply
error: patch failed: drivers/net/sfc/sfc_ethdev.c:26
error: drivers/net/sfc/sfc_ethdev.c: patch does not apply
error: patch failed: drivers/net/sfc/sfc_flow.c:22
error: drivers/net/sfc/sfc_flow.c: patch does not apply
error: drivers/net/sfc/sfc_flow_tunnel.c: already exists in index
error: drivers/net/sfc/sfc_flow_tunnel.h: already exists in index
error: patch failed: drivers/net/sfc/sfc_mae.c:16
error: drivers/net/sfc/sfc_mae.c: patch does not apply
error: patch failed: drivers/net/sfc/sfc_rx.c:13
error: drivers/net/sfc/sfc_rx.c: patch does not apply
Applying: net/sfc: fence off 8 bits in Rx mark for tunnel offload
Patch failed at 0001 net/sfc: fence off 8 bits in Rx mark for tunnel offload
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
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-shz.intel.com
Starting new HTTP connection (1): proxy-shz.intel.com
error: patch failed: drivers/net/sfc/sfc_ef100_rx.c:423
error: drivers/net/sfc/sfc_ef100_rx.c: patch does not apply
error: patch failed: drivers/net/sfc/sfc_ethdev.c:26
error: drivers/net/sfc/sfc_ethdev.c: patch does not apply
error: patch failed: drivers/net/sfc/sfc_rx.c:1181
error: drivers/net/sfc/sfc_rx.c: patch does not apply
Applying: net/sfc: fence off 8 bits in Rx mark for tunnel offload
Patch failed at 0001 net/sfc: fence off 8 bits in Rx mark for tunnel offload
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:[~2021-10-13 18:55 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='746b4b$ekqdss@orsmga008-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=Ivan.Malov@oktetlabs.ru \
    --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).