From: sys_stv@intel.com
To: test-report@dpdk.org, cristian.dumitrescu@intel.com
Subject: [dpdk-test-report] |WARNING| pw(106444) sid(21336) job(PER_PATCH_BUILD879)pipeline: support checksum for variable size headers
Date: 24 Jan 2022 23:21:47 -0800 [thread overview]
Message-ID: <5975f8$e95rjf@orsmga006-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/106444
_apply issues_
Submitter: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Date: 2022-01-24 22:32:49
Reply_mail: 20220124223249.67660-1-cristian.dumitrescu@intel.com
DPDK git baseline:
Repo:dpdk, CommitID: 8a5a91401dc23ddab1ddea3667a17a615a25077f
* Repo: dpdk
eal/linux: log hugepage create errors with filename
While debugging running DPDK service in a container, it is
useful to see which file creation failed. Don't hide this
failure with DEBUG.
Cc: stable@dpdk.org
--
This will be required in git-pw 2.0
Starting new HTTP connection (1): proxy-prc.intel.com
Starting new HTTP connection (1): proxy-prc.intel.com
error: patch failed: lib/pipeline/rte_swx_pipeline_internal.h:309
error: lib/pipeline/rte_swx_pipeline_internal.h: patch does not apply
Applying: pipeline: support checksum for variable size headers
Patch failed at 0001 pipeline: support checksum for variable size headers
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:[~2022-01-25 7:21 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='5975f8$e95rjf@orsmga006-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=cristian.dumitrescu@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).