From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(105881) sid(21188) job(DTS_AUTO_455) [V1] tests/*: removed changing source code before meson build
Date: 26 Jan 2022 02:21:47 -0800 [thread overview]
Message-ID: <746b4b$fuaqus@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1408 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: FAILURE
http://dpdk.org/patch/105881
Subject: [V1] tests/*: removed changing source code before meson build
_Apply issues_
Diff:
tests/TestSuite_ptpclient.py
tests/TestSuite_power_pbf.py
tests/TestSuite_nic_single_core_perf.py
tests/TestSuite_ieee1588.py
framework/project_dpdk.py
DPDK:
commit 8a5a91401dc23ddab1ddea3667a17a615a25077f
Author: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu Dec 23 11:21:58 2021 -0800
Comment: eal/linux: log hugepage create errors with filename
DTS:
commit 993d581241982f0f5b920c928053f898707726b9
Author: Lingli Chen <linglix.chen@intel.com>
Date: Mon Jan 24 16:57:06 2022 +0800
Comment: tests/loopback_virtio_user_server_mode: Modify case sync with testplan
DTS git baseline:
Repo:dts, CommitID: 993d581241982f0f5b920c928053f898707726b9
* Repo: dts
Auto-merging tests/TestSuite_nic_single_core_perf.py
Auto-merging framework/project_dpdk.py
CONFLICT (content): Merge conflict in framework/project_dpdk.py
error: Failed to merge in the changes.
Patch failed at 0001 tests/*: removed changing source code before meson build
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-01-26 10:21 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='746b4b$fuaqus@orsmga008-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).