From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw56075[1/3] eventdev: fix to set positive rte_errno
Date: 19 Jul 2019 16:16:37 -0700 [thread overview]
Message-ID: <ee68f5$7gj9mq@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2958 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/56075
_apply issues_
Submitter: Andrew Rybchenko <arybchenko@solarflare.com>
Date: 2019-07-04 10:03:30
Reply_mail: 1562234612-631-2-git-send-email-arybchenko@solarflare.com
DPDK git baseline:
Repo:dpdk-next-eventdev, CommitID: 7b70f9dbb728754664869934c697949fd5b35fc7
Repo:dpdk, CommitID: c0ed103a027385f14f352d46ff5450826b2746b7
*Repo: dpdk-next-eventdev
* - -ENOSPC The event port was backpressured and unable to enqueue
* one or more events. This error code is only applicable to
* closed systems.
*/
error: patch failed: lib/librte_eventdev/rte_event_eth_tx_adapter.h:332
error: lib/librte_eventdev/rte_event_eth_tx_adapter.h: patch does not apply
Checking patch lib/librte_eventdev/rte_event_timer_adapter.c...
error: while searching for:
&adapter->data->caps,
&adapter->ops);
--
rte_errno = ret;
goto free_memzone;
}
}
error: patch failed: lib/librte_eventdev/rte_event_timer_adapter.c:192
error: lib/librte_eventdev/rte_event_timer_adapter.c: patch does not apply
Checking patch lib/librte_eventdev/rte_eventdev.c...
error: while searching for:
uint16_t *links_map;
int i, diag;
--
rte_errno = -EINVAL;
return 0;
}
error: patch failed: lib/librte_eventdev/rte_eventdev.c:889
error: lib/librte_eventdev/rte_eventdev.c: patch does not apply
Checking patch lib/librte_eventdev/rte_eventdev.h...
error: while searching for:
#ifdef RTE_LIBRTE_EVENTDEV_DEBUG
--
rte_errno = -EINVAL;
return 0;
}
#endif
error: patch failed: lib/librte_eventdev/rte_eventdev.h:1318
error: lib/librte_eventdev/rte_eventdev.h: patch does not apply
*Repo: dpdk
* - -ENOSPC The event port was backpressured and unable to enqueue
* one or more events. This error code is only applicable to
* closed systems.
*/
error: patch failed: lib/librte_eventdev/rte_event_eth_tx_adapter.h:332
error: lib/librte_eventdev/rte_event_eth_tx_adapter.h: patch does not apply
Checking patch lib/librte_eventdev/rte_event_timer_adapter.c...
error: while searching for:
&adapter->data->caps,
&adapter->ops);
--
rte_errno = ret;
goto free_memzone;
}
}
error: patch failed: lib/librte_eventdev/rte_event_timer_adapter.c:192
error: lib/librte_eventdev/rte_event_timer_adapter.c: patch does not apply
Checking patch lib/librte_eventdev/rte_eventdev.c...
error: while searching for:
uint16_t *links_map;
int i, diag;
--
rte_errno = -EINVAL;
return 0;
}
error: patch failed: lib/librte_eventdev/rte_eventdev.c:889
error: lib/librte_eventdev/rte_eventdev.c: patch does not apply
Checking patch lib/librte_eventdev/rte_eventdev.h...
error: while searching for:
#ifdef RTE_LIBRTE_EVENTDEV_DEBUG
--
rte_errno = -EINVAL;
return 0;
}
#endif
error: patch failed: lib/librte_eventdev/rte_eventdev.h:1318
error: lib/librte_eventdev/rte_eventdev.h: patch does not apply
DPDK STV team
next reply other threads:[~2019-07-19 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 23:16 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-05 7:53 sys_stv
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='ee68f5$7gj9mq@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).