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] |SUCCESS| pw(113991-114002) sid(24009) job(DTS_AUTO_1316) [V1, 12/12] test_plans/ice_iavf_fdir: update dts code for dpdk csum change
Date: 18 Jul 2022 01:56:25 -0700	[thread overview]
Message-ID: <11ab82$jgqosd@fmsmga008-auth.fm.intel.com> (raw)

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

Test-Label: Intel-dts-pylama-test
Test-Status: SUCCESS
http://dpdk.org/patch/114002
Subject: [V1,12/12] test_plans/ice_iavf_fdir: update dts code for dpdk csum change

_Testing OK_

Diff:
	tests/TestSuite_kernelpf_iavf.py
	tests/TestSuite_vf_offload.py
	tests/TestSuite_checksum_offload.py
	tests/TestSuite_ice_advanced_iavf_rss.py
	tests/TestSuite_ice_advanced_rss.py
	tests/TestSuite_ice_iavf_fdir.py
	tests/TestSuite_tx_preparation.py
	test_plans/kernelpf_iavf_test_plan.rst
	test_plans/vf_offload_test_plan.rst
	test_plans/ice_advanced_iavf_rss_test_plan.rst
	test_plans/ice_advanced_rss_test_plan.rst
	test_plans/ice_iavf_fdir_test_plan.rst

DPDK:
	commit 4fceceed5b5e9fbf04acffd66239c79d81e79260
	Author: Thomas Monjalon <thomas@monjalon.net>
	Date:   Sun Jul 17 14:58:00 2022 +0200
	Comment: version: 22.07.0

DTS:
	commit 33659110602da75f0e4ee03e54a2a81e71f8ce75
	Author: Lingli Chen <linglix.chen@intel.com>
	Date:   Tue Jul 5 04:16:47 2022 -0400
	Comment: tests/distributor: modify script add novector path expect

DPDK STV team

             reply	other threads:[~2022-07-18  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  8:56 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-18 10:51 sys_stv
2022-07-18 10:51 sys_stv
2022-07-18  8:59 sys_stv
2022-07-18  8:55 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='11ab82$jgqosd@fmsmga008-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).