From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw51373[v9] eal_interrupts: add option for pending callback unregister
Date: 20 Mar 2019 18:19:52 -0700 [thread overview]
Message-ID: <e75792$6e16fo@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2944 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/51373
_apply issues_
Submitter: Jakub Grajciar <jgrajcia@cisco.com>
Date: 2019-03-20 09:26:10
Reply_mail: 20190320092610.9751-1-jgrajcia@cisco.com
DPDK git baseline:
Repo:dpdk-master, CommitID: 1534cc6ab1d93041dcbb0bb6c7f1e111578dffd4
Repo:dpdk-next-eventdev, CommitID: 744407cf7b80f9e5c886c2304211b429febb4394
Repo:dpdk-next-net, CommitID: 9799450f18940bc55d161d5dff31eee031266866
Repo:dpdk-next-crypto, CommitID: 8cc253a267913ee317a54b6a5d2c761d18cc5d5a
Repo:dpdk-next-virtio, CommitID: 7f9cb2162e640ea87772ce0f2cbaf30a2d97d70d
*Repo: dpdk-master
Checking patch lib/librte_eal/bsdapp/eal/eal_interrupts.c...
error: lib/librte_eal/bsdapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/common/include/rte_interrupts.h...
Checking patch lib/librte_eal/linuxapp/eal/eal_interrupts.c...
error: lib/librte_eal/linuxapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/rte_eal_version.map...
Hunk #1 succeeded at 322 (offset 4 lines).
*Repo: dpdk-next-eventdev
Checking patch lib/librte_eal/bsdapp/eal/eal_interrupts.c...
error: lib/librte_eal/bsdapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/common/include/rte_interrupts.h...
Checking patch lib/librte_eal/linuxapp/eal/eal_interrupts.c...
error: lib/librte_eal/linuxapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/rte_eal_version.map...
Hunk #1 succeeded at 322 (offset 4 lines).
*Repo: dpdk-next-net
Checking patch lib/librte_eal/bsdapp/eal/eal_interrupts.c...
error: lib/librte_eal/bsdapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/common/include/rte_interrupts.h...
Checking patch lib/librte_eal/linuxapp/eal/eal_interrupts.c...
error: lib/librte_eal/linuxapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/rte_eal_version.map...
Hunk #1 succeeded at 322 (offset 4 lines).
*Repo: dpdk-next-crypto
Checking patch lib/librte_eal/bsdapp/eal/eal_interrupts.c...
error: lib/librte_eal/bsdapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/common/include/rte_interrupts.h...
Checking patch lib/librte_eal/linuxapp/eal/eal_interrupts.c...
error: lib/librte_eal/linuxapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/rte_eal_version.map...
Hunk #1 succeeded at 322 (offset 4 lines).
*Repo: dpdk-next-virtio
Checking patch lib/librte_eal/bsdapp/eal/eal_interrupts.c...
error: lib/librte_eal/bsdapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/common/include/rte_interrupts.h...
Checking patch lib/librte_eal/linuxapp/eal/eal_interrupts.c...
error: lib/librte_eal/linuxapp/eal/eal_interrupts.c: No such file or directory
Checking patch lib/librte_eal/rte_eal_version.map...
Hunk #1 succeeded at 322 (offset 4 lines).
DPDK STV team
reply other threads:[~2019-03-21 1:19 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='e75792$6e16fo@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).