automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |FAILURE| pw(121514) sid(26353) job(DTS_AUTO_2267) [V2] tests/vm2vm_virtio_pmd: optimization testsuite
Date: 03 Jan 2023 23:41:41 -0800	[thread overview]
Message-ID: <e661bc$i12c2c@orsmga003-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]

Test-Label: Intel-dts-format-test
Test-Status: FAILURE
http://dpdk.org/patch/121514
Subject: [V2] tests/vm2vm_virtio_pmd: optimization testsuite

_Testing issues_

Diff:
	tests/TestSuite_vm2vm_virtio_pmd.py

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 f036e7097fe1079c36d566ebef57c2328f5eb865
	Author: Song Jiale <songx.jiale@intel.com>
	Date:   Wed Jan 4 11:29:43 2023 +0000
	Comment: test_plans/multiprocess: optimize the testplan format

FORMAT test failed information:
isort -c --profile black --line-length 88 --python-version auto .

ERROR: /root/UB2004-64_216/57612f7eeddd404dacc2a46c2a51feeb/dts/tests/TestSuite_vm2vm_virtio_pmd.py Imports are incorrectly sorted and/or formatted.
Skipped 1 files
black --check --line-length 88 --required-version 22.1.0 --target-version py38 --safe .

would reformat tests/TestSuite_vm2vm_virtio_pmd.py

Oh no! 💥 💔 💥
1 file would be reformatted, 375 files would be left unchanged.

Please use format.sh to format your patches and re-submit.

DPDK STV team

             reply	other threads:[~2023-01-04  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  7:41 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-04  8:08 sys_stv
2023-01-04  7:09 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='e661bc$i12c2c@orsmga003-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).