From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org, tadhg.kearney@intel.com
Subject: [dts-test-report] |FAILURE| pw(127194-127195) sid(28126) job(DTS_AUTO_2631) [v1, 2/2] test_plans/power_intel_uncore: add test_plan for newly added test suite
Date: 23 May 2023 02:25:56 -0700 [thread overview]
Message-ID: <76a62b$nksmht@fmsmga003-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Test-Label: Intel-dts-format-test
Test-Status: FAILURE
http://dpdk.org/patch/127195
Subject: [v1,2/2] test_plans/power_intel_uncore: add test_plan for newly added test suite
_Testing issues_
Diff:
tests/TestSuite_power_intel_uncore.py
test_plans/power_intel_uncore_test_plan.rst
test_plans/index.rst
DPDK:
commit a399d7b5a994e335c446d4b15d7622d71dd8848c
Author: Nipun Gupta <nipun.gupta@amd.com>
Date: Wed Jan 4 10:49:36 2023 +0530
Comment: vfio: do not coalesce DMA mappings
DTS:
commit eec72dc0ea5ba5e9b02dfed091e76f9dce0d38b9
Author: Lijuan Tu <lijuan.tu@intel.com>
Date: Fri Apr 28 15:14:05 2023 +0800
Comment: version: 23.07-rc0
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_power_intel_uncore.py
Oh no! 💥 💔 💥
1 file would be reformatted, 368 files would be left unchanged.
Please use format.sh to format your patches and re-submit.
DPDK STV team
next reply other threads:[~2023-05-23 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 9:25 sys_stv [this message]
2023-05-23 9:29 sys_stv
2023-05-23 9:38 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='76a62b$nksmht@fmsmga003-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dts-test-report@dpdk.org \
--cc=tadhg.kearney@intel.com \
--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).