From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, weix.ling@intel.com
Subject: [dts-test-report] |FAILURE| pw(121348) sid(26258) job(DTS_AUTO_2163) [V1] optimization pvp_qemu_multi_paths_port_restart testplan and testsuite
Date: 23 Dec 2022 01:43:56 -0800 [thread overview]
Message-ID: <649fab$laa0n7@fmsmga008-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
Test-Label: Intel-dts-format-test
Test-Status: FAILURE
http://dpdk.org/patch/121348
Subject: [V1] optimization pvp_qemu_multi_paths_port_restart testplan and testsuite
_Testing issues_
Diff:
tests/TestSuite_pvp_qemu_multi_paths_port_restart.py
test_plans/pvp_qemu_multi_paths_port_restart_test_plan.rst
DPDK:
commit 373f4c7de8ff350548cacc3d56e788461677f2c7
Author: David Marchand <david.marchand@redhat.com>
Date: Tue Dec 13 16:07:10 2022 +0100
Comment: ci: drop Travis configuration
DTS:
commit 6640ecb3ebc5347139df2530bdfd2fa5421b6a47
Author: Lingli Chen <linglix.chen@intel.com>
Date: Thu Dec 15 01:42:04 2022 -0500
Comment: tests/rss_to_rte_flow: remove --pkt-filter-mode sync dpdk change
FORMAT test failed information:
isort -c --profile black --line-length 88 --python-version auto .
Skipped 2 files
black --check --line-length 88 --required-version 22.1.0 --target-version py38 --safe .
would reformat tests/TestSuite_pvp_qemu_multi_paths_port_restart.py
Oh no! 💥 💔 💥
1 file would be reformatted, 366 files would be left unchanged.
Please use format.sh to format your patches and re-submit.
DPDK STV team
next reply other threads:[~2022-12-23 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 9:43 sys_stv [this message]
2022-12-23 9:48 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='649fab$laa0n7@fmsmga008-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=test-report@dpdk.org \
--cc=weix.ling@intel.com \
/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).