From: sys_stv@intel.com
To: test-report@dpdk.org, dts-test-report@dpdk.org
Subject: [dts-test-report] |WARNING| pw(108226-108230) sid(21842) job(DTS_AUTO_529) [V3, 5/5] test_plans/*: modify test plan to adapt meson build
Date: 23 Feb 2022 23:47:40 -0800 [thread overview]
Message-ID: <8ea9f5$kcfp9r@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
Test-Label: Intel-dts-suite-test
Test-Status: WARNING
http://dpdk.org/patch/108230
Subject: [V3,5/5] test_plans/*: modify test plan to adapt meson build
_SKIPPED_
Diff:
test_plans/vmdq_dcb_test_plan.rst
test_plans/vm2vm_virtio_user_test_plan.rst
test_plans/vhost_qemu_mtu_test_plan.rst
test_plans/vf_pf_reset_test_plan.rst
test_plans/shutdown_api_test_plan.rst
test_plans/multicast_test_plan.rst
test_plans/metrics_test_plan.rst
test_plans/linux_modules_test_plan.rst
test_plans/kernelpf_iavf_test_plan.rst
test_plans/keep_alive_test_plan.rst
test_plans/ipsec_gw_and_library_test_plan.rst
test_plans/iavf_test_plan.rst
test_plans/generic_flow_api_test_plan.rst
test_plans/flow_classify_test_plan.rst
test_plans/external_mempool_handler_test_plan.rst
test_plans/enable_package_download_in_ice_driver_test_plan.rst
test_plans/ABI_stable_test_plan.rst
test_plans/vf_packet_rxtx_test_plan.rst
test_plans/vdev_primary_secondary_test_plan.rst
test_plans/telemetry_test_plan.rst
DPDK:
commit ee05a93e1e6633d0fdec409faf09f12a2e05b991
Author: Tomasz Duszynski <tduszynski@marvell.com>
Date: Tue Feb 22 09:28:17 2022 +0100
Comment: raw/cnxk_gpio: check pointer before use in self test
DTS:
commit c17f87ae7e0b10af8281373b9017ed77f0c998f3
Author: hanyingya <yingyax.han@intel.com>
Date: Thu Jan 27 10:11:41 2022 +0800
Comment: performance_thread: remove perf test suite
Platform 1: 10.239.251.107
OS: UB2004-64+216
Category: CVL Only | NIC VF | Virtio | NIC PF
Nic: columbiaville_25g | fortville_spirit
DPDK STV team
reply other threads:[~2022-02-24 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='8ea9f5$kcfp9r@fmsmga001-auth.fm.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).