test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Yao, BingX Y" <bingx.y.yao@intel.com>
To: "Zhu, ShuaiX" <shuaix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests/ipfrag:Modify the judgment content.
Date: Tue, 2 Jul 2019 09:51:51 +0000	[thread overview]
Message-ID: <95BCD24840F32441BEA74E0F8A31839E058F3A7F@SHSMSX106.ccr.corp.intel.com> (raw)
In-Reply-To: <1562061118-128994-1-git-send-email-shuaix.zhu@intel.com>

Tested-by: Yao, BingX Y <bingx.y.yao@intel.com>

-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
Sent: Tuesday, July 2, 2019 5:52 PM
To: dts@dpdk.org
Cc: Zhu, ShuaiX <shuaix.zhu@intel.com>
Subject: [dts] [PATCH V1] tests/ipfrag:Modify the judgment content.

The value is modified due to changes in dpdk 19.08.rc0.
commit 4b06b0771f321bd4301075eaff64452261a45a4d

Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
---
 tests/TestSuite_ipfrag.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/TestSuite_ipfrag.py b/tests/TestSuite_ipfrag.py index a6cb629..f6d0373 100644
--- a/tests/TestSuite_ipfrag.py
+++ b/tests/TestSuite_ipfrag.py
@@ -249,7 +249,7 @@ l3fwd_ipv4_route_array[] = {\\\n"
 
                     # fragment offset should be correct
                     frag = pkt.strip_element_layer4("offset")
-                    self.verify((frag == int((idx - 1) * 182)), "Fragment packet frag not match")
+                    self.verify((frag == int((idx - 1) * 181)), 
+ "Fragment packet frag not match")
                     idx += 1
 
     def set_up(self):
--
2.17.2


  reply	other threads:[~2019-07-02  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02  9:51 zhu,shuai
2019-07-02  9:51 ` Yao, BingX Y [this message]
2019-07-03  5:36 ` Tu, Lijuan

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=95BCD24840F32441BEA74E0F8A31839E058F3A7F@SHSMSX106.ccr.corp.intel.com \
    --to=bingx.y.yao@intel.com \
    --cc=dts@dpdk.org \
    --cc=shuaix.zhu@intel.com \
    /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).