From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |WARNING| pw(108713) sid(22142) job(PER_PATCH_BUILD1683)[Bug, 957] IXGBE LSC IRQ configured state is lost on certain link down events
Date: 14 Mar 2022 15:00:48 -0700 [thread overview]
Message-ID: <8ea9f5$ki0ld5@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/108713
_apply issues_
Submitter: bugzilla@dpdk.org
Date: 2022-03-14 21:50:49
Reply_mail: bug-957-3@http.bugs.dpdk.org/
DPDK git baseline:
Repo:dpdk-next-net-intel, CommitID: 397657dcbda21a60597eb854b86ef6cbf74d2589
Repo:dpdk, CommitID: c1d1b94eec5855b3934791a10125e9db5f15298a
* Repo: dpdk-next-net-intel
Starting new HTTP connection (1): proxy-prc.intel.com
error: corrupt patch at line 22
Applying: IXGBE LSC IRQ configured state is lost on certain link down events
Patch failed at 0001 IXGBE LSC IRQ configured state is lost on certain link down events
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
Starting new HTTP connection (1): proxy-prc.intel.com
error: corrupt patch at line 22
Applying: IXGBE LSC IRQ configured state is lost on certain link down events
Patch failed at 0001 IXGBE LSC IRQ configured state is lost on certain link down events
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-03-14 22:01 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='8ea9f5$ki0ld5@fmsmga001-auth.fm.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).