From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(111662-111666) sid(23105) job(DTS_AUTO_1095) [V1, 5/5] test_plans/ice_iavf_ip_fragment_rte_flow:extend mismatch pkts
Date: 23 May 2022 19:34:11 -0700 [thread overview]
Message-ID: <7758ae$m6gg4d@orsmga005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]
Test-Label: Intel-dts-format-test
Test-Status: FAILURE
http://dpdk.org/patch/111666
Subject: [V1,5/5] test_plans/ice_iavf_ip_fragment_rte_flow:extend mismatch pkts
_Testing issues_
Diff:
tests/rte_flow_common.py
tests/TestSuite_ice_ip_fragment_rte_flow.py
test_plans/ice_ip_fragment_rte_flow_test_plan.rst
tests/TestSuite_ice_iavf_ip_fragment_rte_flow.py
test_plans/ice_iavf_ip_fragment_rte_flow_test_plan.rst
DPDK:
commit 981a025741f80b4036f994ed30b04e757299ab19
Author: Stanislaw Kardach <kda@semihalf.com>
Date: Wed May 11 17:07:25 2022 +0200
Comment: test/ring: remove excessive inlining
DTS:
commit f8e47bcdc2991b040ef80dd65fc914df93158290
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Wed May 18 22:09:13 2022 +0800
Comment: format all codes with format.sh
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 /root/UB2004-64_216/c8ec7f36ca2d4d9b8135fba0050964a8/dts/tests/TestSuite_ice_ip_fragment_rte_flow.py
would reformat /root/UB2004-64_216/c8ec7f36ca2d4d9b8135fba0050964a8/dts/tests/TestSuite_ice_iavf_ip_fragment_rte_flow.py
would reformat /root/UB2004-64_216/c8ec7f36ca2d4d9b8135fba0050964a8/dts/tests/rte_flow_common.py
Oh no! 💥 💔 💥
3 files would be reformatted, 348 files would be left unchanged.
Please use format.sh to format your patches and re-submit.
DPDK STV team
next reply other threads:[~2022-05-24 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 2:34 sys_stv [this message]
2022-05-24 2:34 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='7758ae$m6gg4d@orsmga005-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).