From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(113668-113671) sid(23881) job(DTS_AUTO_1287) [V1, 4/4] test_plans/vf_vlan: update dts code for driver change
Date: 05 Jul 2022 04:30:14 -0700 [thread overview]
Message-ID: <9bee9c$if2fsn@orsmga008-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Test-Label: Intel-dts-format-test
Test-Status: FAILURE
http://dpdk.org/patch/113671
Subject: [V1,4/4] test_plans/vf_vlan: update dts code for driver change
_Testing issues_
Diff:
tests/TestSuite_kernelpf_iavf.py
test_plans/kernelpf_iavf_test_plan.rst
tests/TestSuite_vf_vlan.py
test_plans/vf_vlan_test_plan.rst
DPDK:
commit ad42b228c6e26e88b16504153a9338f9b387d2e7
Author: Archana Muniganti <marchana@marvell.com>
Date: Thu Jun 30 16:51:23 2022 +0530
Comment: examples/fips_validation: fix print for zero length payload
DTS:
commit ce08b31ea6b7124ed52cbcb8a261b826a2c28d93
Author: Jiale Song <songx.jiale@intel.com>
Date: Wed Jun 29 17:35:53 2022 +0000
Comment: tests/multiprocess: modify script to suport i40e driver
FORMAT test failed information:
isort -c --profile black --line-length 88 --python-version auto .
Skipped 1 files
black --check --line-length 88 --required-version 22.1.0 --target-version py38 --safe .
would reformat tests/TestSuite_vf_vlan.py
would reformat tests/TestSuite_kernelpf_iavf.py
Oh no! 💥 💔 💥
2 files would be reformatted, 355 files would be left unchanged.
Please use format.sh to format your patches and re-submit.
DPDK STV team
next reply other threads:[~2022-07-05 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 11:30 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-06 1:41 sys_stv
2022-07-05 11:24 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='9bee9c$if2fsn@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).