test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Lin, Xueqin" <xueqin.lin@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>,
	xueqin.lin <xlin15@ecsmtp.sh.intel.com>,
	 "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] tests_ftag: fix expected output time when striping port glort ID
Date: Tue, 16 Aug 2016 06:35:59 +0000	[thread overview]
Message-ID: <0D300480287911409D9FF92C1FA2A3351A7C3C15@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <86228AFD5BCD8E4EBFD2B90117B5E81E2226F0AA@SHSMSX103.ccr.corp.intel.com>

Hi Marvin,

This patch has merged for RubyRapid card, fixed file is rrc.py.
Another patch is new and for BoulderRapid card, file is br.py.

Best regards,
Xueqin
> -----Original Message-----
> From: Liu, Yong
> Sent: Tuesday, August 16, 2016 2:18 PM
> To: xueqin.lin; dts@dpdk.org
> Cc: Lin, Xueqin
> Subject: RE: [dts][PATCH] tests_ftag: fix expected output time when striping
> port glort ID
> 
> Hi Qin, your patch hasn't been merged, so you need to send out patch with all
> the changes.
> 
> > -----Original Message-----
> > From: xueqin.lin [mailto:xlin15@ecsmtp.sh.intel.com]
> > Sent: Tuesday, August 16, 2016 2:13 PM
> > To: Liu, Yong; dts@dpdk.org
> > Cc: Lin, Xueqin
> > Subject: [dts][PATCH] tests_ftag: fix expected output time when striping
> > port glort ID
> >
> > From: Xueqin Lin <xueqin.lin@intel.com>
> >
> > It is impossible to wait some long time for expected output, just fix as
> > default value.
> >
> >
> > diff --git a/nics/rrc.py b/nics/rrc.py
> > index 62dc8d2..a6ac175 100644
> > --- a/nics/rrc.py
> > +++ b/nics/rrc.py
> > @@ -259,7 +259,7 @@ class RedRockCanyou(NetDevice):
> >              return None
> >          else:
> >              port_value = res.group(2)
> > -        out = self.ctrl_crb.send_expect("show stacking logical-port all",
> > "<0>%",10000)
> > +        out = self.ctrl_crb.send_expect("show stacking logical-port all",
> > "<0>%")
> >          pattern = r"([0-9a-z]{6})+(\s)+(%s)+" %port_value
> >          s = re.compile(pattern)
> >          res = s.search(out)
> > --
> > 2.5.5

  reply	other threads:[~2016-08-16  6:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1471328009-15507-1-git-send-email-xlin15@shecgisg005.sh.intel.com>
2016-08-16  6:17 ` Liu, Yong
2016-08-16  6:35   ` Lin, Xueqin [this message]
     [not found] <1471500985-3542-1-git-send-email-xlin15@shecgisg005.sh.intel.com>
2016-08-18  7:42 ` Liu, Yong

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=0D300480287911409D9FF92C1FA2A3351A7C3C15@SHSMSX103.ccr.corp.intel.com \
    --to=xueqin.lin@intel.com \
    --cc=dts@dpdk.org \
    --cc=xlin15@ecsmtp.sh.intel.com \
    --cc=yong.liu@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).