From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(104583) sid(20696) job(DTS_AUTO967) [V2] tests/unit_tests_eal:remove strict timing requirements some tests
Date: 22 Nov 2021 19:07:40 -0800 [thread overview]
Message-ID: <722c05$eq2okj@orsmga007-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/104583
Subject: [V2] tests/unit_tests_eal:remove strict timing requirements some tests
_Apply issues_
Diff:
tests/TestSuite_unit_tests_eal.py
test_plans/unit_tests_eal_test_plan.rst
DPDK:
commit 0c6e27549c03695f85d949f5195a166b449b419c
Author: Thomas Monjalon <thomas@monjalon.net>
Date: Wed Nov 17 20:19:47 2021 +0100
Comment: version: 21.11-rc3
DTS:
commit f78b33713dcf275f9458ef3e0b60c1c60d0c1355
Author: DongJunX <junx.dong@intel.com>
Date: Wed Nov 17 17:26:30 2021 +0800
Comment: framework/test_case: removed bind_nic_driver common func to framework
DTS git baseline:
Repo:dts, CommitID: f78b33713dcf275f9458ef3e0b60c1c60d0c1355
* Repo: dts
Auto-merging tests/TestSuite_unit_tests_eal.py
CONFLICT (content): Merge conflict in tests/TestSuite_unit_tests_eal.py
Auto-merging test_plans/unit_tests_eal_test_plan.rst
error: Failed to merge in the changes.
Patch failed at 0001 tests/unit_tests_eal:remove strict timing requirements some tests
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:[~2021-11-23 3:07 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='722c05$eq2okj@orsmga007-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@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).