From: sys_stv@intel.com
To: test-report@dpdk.org, bugzilla@dpdk.org
Subject: compilation|WARNING| pw(138408) sid(31525) job(PER_PATCH_BUILD11442)[DPDK/ethdev, Bug, 1403] PMD: IDPF segfaults during init on GCP baremetal
Date: 14 Mar 2024 13:53:14 -0700 [thread overview]
Message-ID: <0fb38d$bprdk@fmviesa009-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/138408
_apply issues_
Submitter: <bugzilla@dpdk.org>
Date: 2024-03-14 20:41:52
Reply_mail: <bug-1403-3@http.bugs.dpdk.org/>
DPDK git baseline:
Repo:dpdk-next-net-intel, CommitID: 19082c1fac430c74bb4b1c101edd12d88928e7c2
Repo:dpdk, CommitID: cd218549b686d6be394ef3b171eafa16c038bfe3
* Repo: dpdk-next-net-intel
This will be required in git-pw 2.0
error: corrupt patch at line 6
Applying: PMD: IDPF segfaults during init on GCP baremetal
Patch failed at 0001 PMD: IDPF segfaults during init on GCP baremetal
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
error: corrupt patch at line 6
Applying: PMD: IDPF segfaults during init on GCP baremetal
Patch failed at 0001 PMD: IDPF segfaults during init on GCP baremetal
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:[~2024-03-14 20:53 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='0fb38d$bprdk@fmviesa009-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=bugzilla@dpdk.org \
--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).