From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A80E243101; Fri, 25 Aug 2023 16:05:31 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8302640695; Fri, 25 Aug 2023 16:05:31 +0200 (CEST) Received: from mail-yw1-f173.google.com (mail-yw1-f173.google.com [209.85.128.173]) by mails.dpdk.org (Postfix) with ESMTP id CD8A5400D5 for ; Fri, 25 Aug 2023 16:05:29 +0200 (CEST) Received: by mail-yw1-f173.google.com with SMTP id 00721157ae682-58d40c2debeso11475297b3.2 for ; Fri, 25 Aug 2023 07:05:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1692972329; x=1693577129; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ANEmiUHybmqlLi9hLJhcMUwgO4wvqKMIZW1ADMo30QI=; b=ZcGHFzXmPF0BzxdZcj7+3FtJwGgV0hqtZiHTDo1r7RWDFdGUIntApgUEGnopyx76UM rmRCduUbTMdGTkr2o+ecBAFR/FNlDe6UIc0ZlkmJIQyGoUbgT6nQShbpaQhRgJfl2Jdw grj/on8C0gYIUotRVKheaRTAVP9rQgdbV/yMo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692972329; x=1693577129; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ANEmiUHybmqlLi9hLJhcMUwgO4wvqKMIZW1ADMo30QI=; b=a5oPhoaNL4Ec3bkslORL49lg5vnRdbbVu54BmqyMLt63kBKx7Nzh7ybuWr6bfmA93H bKe3Pco8XMbXRJOA6DstPQCbkUEWYrqjsMZItuThTj+3l6xV2hInnEDTkJiHI7XbdcNQ isGvLGUxHLbWGRq9Zv6rI0GFMJIqO+KbeGxWAoD2hZrqOnsPkjwZs+Uh9EdIc7dc1/H0 An++nXxY/xEkEQwnCu/2EsRSfvtHFAyIKbtr2f6zgT637RdvibqLq9uhyMN/IGiN0cpK gRr5NXFvqFhyJA2v8+9pCt+dJ0DdW/65cs8SRrzxC/gaKE7afC0CqTphk1yNos91CWMN dsMw== X-Gm-Message-State: AOJu0YzqPCd8VDWANgixrsN0khAuJQXPMSrQGW1IwIKVjDywnxnCtz86 MToBvkrX+6DWupcVb1MlCEEZSsXtQhUTm7MjAsjR2SktcKib7QrzTEzbQA== X-Google-Smtp-Source: AGHT+IESo90MdQbfwL0gXEEwOC0kzdjCioPcShFX15mmO1efez4WgGA0zJlsPkPkNOS1rYy9XxbDL75poJRefAFl5Cw= X-Received: by 2002:a0d:d712:0:b0:570:28a9:fe40 with SMTP id z18-20020a0dd712000000b0057028a9fe40mr18308533ywd.5.1692972328830; Fri, 25 Aug 2023 07:05:28 -0700 (PDT) MIME-Version: 1.0 References: <35340484-1d7e-7e5f-cad4-c965ba541397@oktetlabs.ru> <9ce9d7fd-4051-6d51-26bb-7e96e98c677e@oktetlabs.ru> <781ca146-955f-85af-5727-66015ae1d326@oktetlabs.ru> <7734826a-840d-d0d9-e7a5-91951223398c@oktetlabs.ru> <9d920676-485d-3b4d-ca20-2b5ea3a5b606@oktetlabs.ru> <873c7972-3e5a-9e82-9449-4d12b2c96032@oktetlabs.ru> In-Reply-To: From: Adam Hassick Date: Fri, 25 Aug 2023 10:06:00 -0400 Message-ID: Subject: Re: Setting up DPDK PMD Test Suite To: Andrew Rybchenko Cc: Patrick Robb , Konstantin Ushakov , ci@dpdk.org Content-Type: multipart/alternative; boundary="0000000000004660700603bfd6d9" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org --0000000000004660700603bfd6d9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Andrew, Two of our systems (the Test Engine runner and the DUT host) are running Ubuntu 20.04 LTS, however this morning I noticed that the tester system (the one having issues) is running Ubuntu 22.04 LTS. This could be the source of the problem. I encountered a dependency issue trying to run the Test Engine on 22.04 LTS, so I downgraded the system. Since the tester is also the host having connection issues, I will try downgrading that system to 20.04, and see if that changes anything. I did try passing in the "--vg-rcf" argument to the run.sh script of the test suite after installing valgrind, but there was no additional output that I saw. I will try pulling in the changes you've pushed up, and will see if that fixes anything. Thanks, Adam On Fri, Aug 25, 2023 at 9:57=E2=80=AFAM Andrew Rybchenko < andrew.rybchenko@oktetlabs.ru> wrote: > Hello Adam, > > On 8/24/23 23:54, Andrew Rybchenko wrote: > > I'd like to try to repeat the problem locally. Which Linux distro is > running on test engine and agents? > > In fact I know one problem with Debian 12 and Fedora 38 and we have > patch in review to fix it, however, the behaviour is different in > this case, so it is unlike the same problem. > > > I've just published a new tag which fixes known test engine side problems > on Debian 12 and Fedora 38. > > > One more idea is to install valgrind on the test engine host and > run with option --vg-rcf to check if something weird is happening. > > What I don't understand right now is why I see just one failed attempt > to connect in your log.txt and then Logger shutdown after 9 minutes. > > Andrew. > > On 8/24/23 23:29, Adam Hassick wrote: > > > Is there any firewall in the network or on test hosts which could bloc= k > incoming TCP connection to the port 23571 > > from the host where you > run test engine? > > Our test engine host and the testbed are on the same subnet. The > connection does work sometimes. > > > If behaviour the same on the next try and you see that test agent is > kept running, could you check using > > > > # netstat -tnlp > > > > that Test Agent is listening on the port and try to establish TCP > connection from test agent using > > > > $ telnet iol-dts-tester.dpdklab.iol.unh.edu > > 23571 > > > > > > and check if TCP connection could be established. > > I was able to replicate the same behavior again, where it hangs while RCF > is trying to start. > Running this command, I see this in the output: > > tcp 0 0 0.0.0.0:23571 > 0.0.0.0:* LISTEN > 18599/ta > > So it seems like it is listening on the correct port. > Additionally, I was able to connect to the Tester machine from our Test > Engine host using telnet. It printed the PID of the process once the > connection was opened. > > I tried running the "ta" application manually on the command line, and it > didn't print anything at all. > Maybe the issue is something on the Test Engine side. > > On Thu, Aug 24, 2023 at 2:35=E2=80=AFPM Andrew Rybchenko < > andrew.rybchenko@oktetlabs.ru > > wrote: > > Hi Adam, > > > On the tester host (which appears to be the Peer agent), there > are four processes that I see running, which look like the test > agent processes. > > Before the next try I'd recommend to kill these processes. > > Is there any firewall in the network or on test hosts which could > block incoming TCP connection to the port 23571 > > from the host > where you run test engine? > > If behaviour the same on the next try and you see that test agent is > kept running, could you check using > > # netstat -tnlp > > that Test Agent is listening on the port and try to establish TCP > connection from test agent using > > $ telnet iol-dts-tester.dpdklab.iol.unh.edu > > 23571 > > > > and check if TCP connection could be established. > > Another idea is to login Tester under root as testing does, get > start TA command from the log and try it by hands without -n and > remove extra escaping. > > # sudo PATH=3D${PATH}:/tmp/linux_x86_root_76872_1692885663_1 > > LD_LIBRARY_PATH=3D${LD_LIBRARY_PATH}${LD_LIBRARY_PATH:+:}/tmp/linux_x86_r= oot_76872_1692885663_1 > /tmp/linux_x86_root_76872_1692885663_1/ta Peer 23571 > host=3Diol-dts-tester.dpdklab.iol.unh.edu: > port=3D23571:user=3Droot:key=3D/opt/tsf/keys/id_ed25519:ssh_port=3D22:cop= y_timeout=3D15:kill_timeout=3D15:sudo=3D:shell=3D > > Hopefully in this case test agent directory remains in the /tmp and > you don't need to copy it as testing does. > May be output could shed some light on what's going on. > > Andrew. > > On 8/24/23 17:30, Adam Hassick wrote: > > Hi Andrew, > > This is the output that I see in the terminal when this failure > occurs, after the test agent binaries build and the test engine > starts: > > Platform default build - pass > Simple RCF consistency check succeeded > --->>> Starting Logger...done > --->>> Starting RCF...rcf_net_engine_connect(): Connection timed > out iol-dts-tester.dpdklab.iol.unh.edu:23571 > > > > Then, it hangs here until I kill the "te_rcf" and "te_tee" > processes. I let it hang for around 9 minutes. > > On the tester host (which appears to be the Peer agent), there are > four processes that I see running, which look like the test agent > processes. > > ta.Peer is an empty file. I've attached the log.txt from this run. > > - Adam > > On Thu, Aug 24, 2023 at 4:22=E2=80=AFAM Andrew Rybchenko > > > wrote: > > Hi Adam, > > Yes, TE_RCFUNIX_TIMEOUT is in seconds. I've double-checked > that it goes to 'copy_timeout' in ts-conf/rcf.conf. > Description in in doc/sphinx/pages/group_te_engine_rcf.rst > says that copy_timeout is in seconds and implementation in > lib/rcfunix/rcfunix.c passes the value to select() tv_sec. > Theoretically select() could be interrupted by signal, but I > think it is unlikely here. > > I'm not sure that I understand what do you mean by RCF > connection timeout. Does it happen on TE startup when RCF > starts test agents. If so, TE_RCFUNIX_TIMEOUT could help. Or > does it happen when tests are in progress, e.g. in the middle > of a test. If so, TE_RCFUNIX_TIMEOUT is unrelated and most > likely either host with test agent dies or test agent itself > crashes. It would be easier for me if classify it if you share > text log (log.txt, full or just corresponding fragment with > some context). Also content of ta.DPDK or ta.Peer file > depending on which agent has problems could shed some light. > Corresponding files contain stdout/stderr of test agents. > > Andrew. > > On 8/23/23 17:45, Adam Hassick wrote: > > Hi Andrew, > > I've set up a test rig repository here, and have created > configurations for our development testbed based off of the > examples. > We've been able to get the test suite to run manually on > Mellanox CX5 devices once. > However, we are running into an issue where, when RCF starts, > the RCF connection times out very frequently. We aren't sure > why this is the case. > It works sometimes, but most of the time when we try to run > the test engine, it encounters this issue. > I've tried changing the RCF port by setting > "TE_RCF_PORT=3D" and rebooting the testbed > machines. Neither seems to fix the issue. > > It also seems like the timeout takes far longer than 60 > seconds, even when running "export TE_RCFUNIX_TIMEOUT=3D60" > before I try to run the test suite. > I assume the unit for this variable is seconds? > > Thanks, > Adam > > On Mon, Aug 21, 2023 at 10:19=E2=80=AFAM Adam Hassick > > > wrote: > > Hi Andrew, > > Thanks, I've cloned the example repository and will start > setting up a configuration for our development testbed > today. I'll let you know if I run into any difficulties > or have any questions. > > - Adam > > On Sun, Aug 20, 2023 at 4:40=E2=80=AFAM Andrew Rybchenko > > > wrote: > > Hi Adam, > > I've published > https://github.com/ts-factory/ts-rigs-sample > > . > Hopefully it will help to define your test rigs and > successfully run some tests manually. Feel free to > ask any questions and I'll answer here and try to > update documentation. > > Meanwhile I'll prepare missing bits for steps (2) and > (3). > Hopefully everything is in place for step (4), but we > need to make steps (2) and (3) first. > > Andrew. > > On 8/18/23 21:40, Andrew Rybchenko wrote: > > Hi Adam, > > > I've conferred with the rest of the team, and we > think it would be best to move forward with mainly > option B. > > OK, I'll provide the sample on Monday for you. It is > almost ready right now, but I need to double-check > it before publishing. > > Regards, > Andrew. > > On 8/17/23 20:03, Adam Hassick wrote: > > Hi Andrew, > > I'm adding the CI mailing list to this > conversation. Others in the community might find > this conversation valuable. > > We do want to run testing on a regular basis. The > Jenkins integration will be very useful for us, as > most of our CI is orchestrated by Jenkins. > I've conferred with the rest of the team, and we > think it would be best to move forward with mainly > option B. > If you would like to know anything about our > testbeds that would help you with creating an > example ts-rigs repo, I'd be happy to answer any > questions you have. > > We have multiple test rigs (we call these > "DUT-tester pairs") that we run our existing > hardware testing on, with differing network > hardware and CPU architecture. I figured this might > be an important detail. > > Thanks, > Adam > > On Thu, Aug 17, 2023 at 11:44=E2=80=AFAM Andrew Rybchenko > > > wrote: > > Greatings Adam, > > I'm happy to hear that you're trying to bring > it up. > > As I understand the final goal is to run it on > regular basis. So, we need to make it properly > from the very beginning. > Bring up of all features consists of 4 steps: > > 1. Create site-specific repository (we call it > ts-rigs) which contains information about test > rigs and other site-specific information like > where to send mails, where to store logs etc. > It is required for manual execution as well, > since test rigs description is essential. I'll > return to the topic below. > > 2. Setup logs storage for automated runs. > Basically it is a disk space plus apache2 web > server with few CGI scripts which help a lot to > save disk space. > > 3. Setup Bublik web application which provides > web interface to view testing results. Same as > https://ts-factory.io/bublik > > > > 4. Setup Jenkins to run tests on regularly, > save logs in log storage (2) and import it to > bublik (3). > > Last few month we spent on our homework to make > it simpler to bring up automated execution > using Jenkins - > https://github.com/ts-factory/te-jenkins > > > Corresponding bits in dpdk-ethdev-ts will be > available tomorrow. > > Let's return to the step (1). > > Unfortunately there is no publicly available > example of the ts-rigs repository since > sensitive site-specific information is located > there. But I'm ready to help you to create it > for UNH. I see two options here: > > (A) I'll ask questions and based on your > answers will create the first draft with my > comments. > > (B) I'll make a template/example ts-rigs repo, > publish it and you'll create UNH ts-rigs based > on it. > > Of course, I'll help to debug and finally bring > it up in any case. > > (A) is a bit simpler for me and you, but (B) is > a bit more generic and will help other > potential users to bring it up. > We can combine (A)+(B). I.e. start from (A). > What do you think? > > Thanks, > Andrew. > > On 8/17/23 15:18, Konstantin Ushakov wrote: > > Greetings Adam, > > > Thanks for contacting us. I copy Andrew who > would be happy to help > > Thanks, > Konstantin > > On 16 Aug 2023, at 21:50, Adam Hassick > > > wrote: > > =EF=BB=BF > Greetings Konstantin, > > I am in the process of setting up the DPDK > Poll Mode Driver test suite as an addition to > our testing coverage for DPDK at the UNH lab. > > I have some questions about how to set the > test suite arguments. > > I have been able to configure the Test Engine > to connect to the hosts in the testbed. The > RCF, Configurator, and Tester all begin to > run, however the prelude of the test suite > fails to run. > > > https://ts-factory.io/doc/dpdk-ethdev-ts/index.html#test-parameters > > > > The documentation mentions that there are > several test parameters for the test suite, > like for the IUT test link MAC, etc. These > seem like they would need to be set somewhere > to run many of the tests. > > I see in the Test Engine documentation, there > are instructions on how to create new > parameters for test suites in the Tester > configuration, but there is nothing in the > user guide or in the Tester guide for how to > set the arguments for the parameters when > running the test suite that I can find. I'm > not sure if I need to write my own Tester > config, or if I should be setting these in > some other way. > > How should these values be set? > > I'm also not sure what environment > variables/arguments are strictly necessary or > which are optional. > > Regards, > Adam > > -- *Adam Hassick* > Senior Developer > UNH InterOperability Lab > ahassick@iol.unh.edu > > iol.unh.edu > > +1 (603) 475-8248 > > > > > -- *Adam Hassick* > Senior Developer > UNH InterOperability Lab > ahassick@iol.unh.edu > > iol.unh.edu > > +1 (603) 475-8248 > > > > > > -- *Adam Hassick* > Senior Developer > UNH InterOperability Lab > ahassick@iol.unh.edu > > iol.unh.edu > > +1 (603) 475-8248 > > > > -- *Adam Hassick* > Senior Developer > UNH InterOperability Lab > ahassick@iol.unh.edu > > iol.unh.edu > +1 (603) 475-8248 > > > > > -- *Adam Hassick* > Senior Developer > UNH InterOperability Lab > ahassick@iol.unh.edu > > iol.unh.edu > +1 (603) 475-8248 > > > > > -- > *Adam Hassick* > Senior Developer > UNH InterOperability Lab > ahassick@iol.unh.edu > iol.unh.edu > +1 (603) 475-8248 > > > > --=20 *Adam Hassick* Senior Developer UNH InterOperability Lab ahassick@iol.unh.edu iol.unh.edu +1 (603) 475-8248 --0000000000004660700603bfd6d9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Andrew,

Two of our systems (the = Test Engine=20 runner and the DUT host) are running Ubuntu 20.04 LTS, however this morning= I noticed that the tester system (the one having issues) is running Ubuntu 22.04 LTS.
This could be the source of the problem. I encoun= tered a dependency issue trying to run the Test Engine on 22.04 LTS, so I d= owngraded the system. Since the tester is also the host having connection i= ssues, I will try downgrading that system to 20.04, and see if that changes= anything.

I did try passing in the "--vg= -rcf" argument to the run.sh script of the test suite after installing= valgrind, but there was no additional output that I saw.

I will try pulling in the changes you've pushed up, and will see if th= at fixes anything.

Thanks,
Adam

On= Fri, Aug 25, 2023 at 9:57=E2=80=AFAM Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> wrot= e:
=20 =20 =20
Hello Adam,

On 8/24/23 23:54, Andrew Rybchenko wrote:
I'd like to try to repeat the problem locally. Which Linux distro is running on test engine and agents?

In fact I know one problem with Debian 12 and Fedora 38 and we have
patch in review to fix it, however, the behaviour is different in
this case, so it is unlike the same problem.

I've just published a new tag which fixes known test engine side problems on Debian 12 and Fedora 38.


One more idea is to install valgrind on the test engine host and
run with option --vg-rcf to check if something weird is happening.

What I don't understand right now is why I see just one failed attempt
to connect in your log.txt and then Logger shutdown after 9 minutes.

Andrew.

On 8/24/23 23:29, Adam Hassick wrote:
=C2=A0> Is there any firewall in the net= work or on test hosts which could block incoming TCP connection to the port 23571 <http://iol-dts-tester.dpdklab.iol.unh.edu:23571> fro= m the host where you run test engine?

Our test engine host and the testbed are on the same subnet. The connection does work sometimes.

=C2=A0> If behaviour the same on the next try and you see that test agent is kept running, could you check using
=C2=A0>
=C2=A0> # netstat -tnlp
=C2=A0>
=C2=A0> that Test Agent is listening on the port and try to establish TCP connection from test agent using
=C2=A0>
=C2=A0> $ telnet iol-dts-tester.dpdklab.iol.unh.edu <http://iol-dts-tester.dpdklab.iol.unh.edu:23571> 235= 71 <http://iol-dts-tester.dpdklab.iol.unh.edu:23571>
=C2=A0>
=C2=A0> and check if TCP connection could be established.

I was able to replicate the same behavior again, where it hangs while RCF is trying to start.
Running this command, I see this in the output:

tcp =C2=A0 =C2=A0 =C2=A0 =C2=A00 =C2=A0 =C2=A0 =C2=A00 0.0.0.0:23571 <http://0.0.0= .0:23571>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 0.0.0.0:* =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LISTEN =C2=A0 =C2=A0 =C2=A018599/ta

So it seems like it is listening on the correct port.
Additionally, I was able to connect to the Tester machine from our Test Engine host using telnet. It printed the PID of the process once the connection was opened.

I tried running the "ta" application manually on the comm= and line, and it didn't print anything at all.
Maybe the issue is something on the Test Engine side.

On Thu, Aug 24, 2023 at 2:35=E2=80=AFPM Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru = <mailto:andrew.rybchenko@oktetlabs.ru>> wrote:

=C2=A0=C2=A0=C2=A0 Hi Adam,

=C2=A0=C2=A0=C2=A0=C2=A0 > On the tester host (which appears to = be the Peer agent), there
=C2=A0=C2=A0=C2=A0 are four processes that I see running, which loo= k like the test
=C2=A0=C2=A0=C2=A0 agent processes.

=C2=A0=C2=A0=C2=A0 Before the next try I'd recommend to kill th= ese processes.

=C2=A0=C2=A0=C2=A0 Is there any firewall in the network or on test = hosts which could
=C2=A0=C2=A0=C2=A0 block incoming TCP connection to the port 23571
=C2=A0=C2=A0=C2=A0 <http://iol-dts-tester.dpdklab.iol.unh.edu= :23571> from the host
=C2=A0=C2=A0=C2=A0 where you run test engine?

=C2=A0=C2=A0=C2=A0 If behaviour the same on the next try and you se= e that test agent is
=C2=A0=C2=A0=C2=A0 kept running, could you check using

=C2=A0=C2=A0=C2=A0 # netstat -tnlp

=C2=A0=C2=A0=C2=A0 that Test Agent is listening on the port and try= to establish TCP
=C2=A0=C2=A0=C2=A0 connection from test agent using

=C2=A0=C2=A0=C2=A0 $ telnet iol-dts-tester.dpdklab.iol.unh.edu
=C2=A0=C2=A0=C2=A0 <http://iol-dts-tester.dpdklab.iol.unh.edu= :23571> 23571
=C2=A0=C2=A0=C2=A0 <http://iol-dts-tester.dpdklab.iol.unh.edu= :23571>

=C2=A0=C2=A0=C2=A0 and check if TCP connection could be established= .

=C2=A0=C2=A0=C2=A0 Another idea is to login Tester under root as te= sting does, get
=C2=A0=C2=A0=C2=A0 start TA command from the log and try it by hand= s without -n and
=C2=A0=C2=A0=C2=A0 remove extra escaping.

=C2=A0=C2=A0=C2=A0 # sudo PATH=3D${PATH}:/tmp/linux_x86_root_76872_= 1692885663_1
=C2=A0=C2=A0=C2=A0 LD_LIBRARY_PATH=3D${LD_LIBRARY_PATH}${LD_LIBRARY_PATH:+:}/tmp/linux_x86_roo= t_76872_1692885663_1 /tmp/linux_x86_root_76872_1692885663_1/ta Peer 23571 host=3Diol-dts-tester.dpdklab.iol.unh.edu:port=3D23571:user=3Droot:key=3D/o= pt/tsf/keys/id_ed25519:ssh_port=3D22:copy_timeout=3D15:kill_timeout=3D15:su= do=3D:shell=3D

=C2=A0=C2=A0=C2=A0 Hopefully in this case test agent directory rema= ins in the /tmp and
=C2=A0=C2=A0=C2=A0 you don't need to copy it as testing does.
=C2=A0=C2=A0=C2=A0 May be output could shed some light on what'= s going on.

=C2=A0=C2=A0=C2=A0 Andrew.

=C2=A0=C2=A0=C2=A0 On 8/24/23 17:30, Adam Hassick wrote:
=C2=A0=C2=A0=C2=A0 Hi Andrew,

=C2=A0=C2=A0=C2=A0 This is the output that I see in the terminal = when this failure
=C2=A0=C2=A0=C2=A0 occurs, after the test agent binaries build an= d the test engine
=C2=A0=C2=A0=C2=A0 starts:

=C2=A0=C2=A0=C2=A0 Platform default build - pass
=C2=A0=C2=A0=C2=A0 Simple RCF consistency check succeeded
=C2=A0=C2=A0=C2=A0 --->>> Starting Logger...done
=C2=A0=C2=A0=C2=A0 --->>> Starting RCF...rcf_net_engine_= connect(): Connection timed
=C2=A0=C2=A0=C2=A0 out iol-dts-tester.dpdklab.iol.unh.edu:2357= 1
=C2=A0=C2=A0=C2=A0 <http://iol-dts-tester.dpdklab.iol.unh.e= du:23571>

=C2=A0=C2=A0=C2=A0 Then, it hangs here until I kill the "te_= rcf" and "te_tee"
=C2=A0=C2=A0=C2=A0 processes. I let it hang for around 9 minutes.

=C2=A0=C2=A0=C2=A0 On the tester host (which appears to be the Pe= er agent), there are
=C2=A0=C2=A0=C2=A0 four processes that I see running, which look = like the test agent
=C2=A0=C2=A0=C2=A0 processes.

=C2=A0=C2=A0=C2=A0 ta.Peer is an empty file. I've attached th= e log.txt from this run.

=C2=A0=C2=A0=C2=A0 =C2=A0- Adam

=C2=A0=C2=A0=C2=A0 On Thu, Aug 24, 2023 at 4:22=E2=80=AFAM Andrew= Rybchenko
=C2=A0=C2=A0=C2=A0 <andrew.rybchenko@oktetlabs.ru
=C2=A0=C2=A0=C2=A0 <mailto:andrew.rybchenko@oktetlabs.ru>> w= rote:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Hi Adam,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Yes, TE_RCFUNIX_TIMEOU= T is in seconds. I've double-checked
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 that it goes to 'c= opy_timeout' in ts-conf/rcf.conf.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Description in in doc/sphinx/pages/group_te_engine_rcf.rst
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 says that copy_timeout= is in seconds and implementation in
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 lib/rcfunix/rcfunix.c = passes the value to select() tv_sec.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Theoretically select()= could be interrupted by signal, but I
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 think it is unlikely h= ere.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I'm not sure that = I understand what do you mean by RCF
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 connection timeout. Do= es it happen on TE startup when RCF
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 starts test agents. If= so, TE_RCFUNIX_TIMEOUT could help. Or
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 does it happen when te= sts are in progress, e.g. in the middle
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 of a test. If so, TE_R= CFUNIX_TIMEOUT is unrelated and most
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 likely either host wit= h test agent dies or test agent itself
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 crashes. It would be e= asier for me if classify it if you share
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 text log (log.txt, ful= l or just corresponding fragment with
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 some context). Also co= ntent of ta.DPDK or ta.Peer file
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 depending on which age= nt has problems could shed some light.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Corresponding files co= ntain stdout/stderr of test agents.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Andrew.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 On 8/23/23 17:45, Adam= Hassick wrote:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 Hi Andrew,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I've set up a te= st rig repository here, and have created
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 configurations for o= ur development testbed based off of the
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 examples.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 We've been able = to get the test suite to run manually on
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Mellanox CX5 devices= once.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 However, we are runn= ing into an issue where, when RCF starts,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the RCF connection t= imes out very frequently. We aren't sure
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 why this is the case= .
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 It works sometimes, = but most of the time when we try to run
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the test engine, it = encounters this issue.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I've tried chang= ing the RCF port by setting
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "TE_RCF_PORT=3D= <some port number>" and rebooting the testbed
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 machines. Neither se= ems to fix the issue.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 It also seems like t= he timeout takes far longer than 60
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 seconds, even when r= unning "export TE_RCFUNIX_TIMEOUT=3D60"
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 before I try to run = the test suite.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I assume the unit fo= r this variable is seconds?

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Thanks,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Adam

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 On Mon, Aug 21, 2023= at 10:19=E2=80=AFAM Adam Hassick
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <ahassick@iol.unh.edu <m= ailto:ahassick@iol.unh.edu>> wrote:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 Hi Andrew,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 Thanks, I've cloned the example repository and will start
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 setting up a configuration for our development testbed
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 today. I'll let you know if I run into any difficulties
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 or have any questions.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 =C2=A0- Adam

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 On Sun, Aug 20, 2023 at 4:40=E2=80=AFAM Andrew Rybchenko
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 <= andrew.rybchenko@oktetlabs.ru
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 <= mailto:andrew.rybchenko@oktetlabs.ru>> wrote:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 Hi Adam,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 I've published
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 https://github.com/ts-factory/ts-rigs-sample
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0
<https://github.com/ts-factory/ts-rigs-sample>.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 Hopefully it will help to define your test rigs and
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 successfully run some tests manually. Feel free to
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 ask any questions and I'll answer here and try to
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 update documentation.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 Meanwhile I'll prepare missing bits for steps (2) and
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 (3).
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 Hopefully everything is in place for step (4), but we
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 need to make steps (2) and (3) first.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 Andrew.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 On 8/18/23 21:40, Andrew Rybchenko wrote:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Hi Adam,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 > I've conferred with the rest of the team, and we
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 think it would be best to move forward with mainly
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 option B.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 OK, I'll provide the sample on Monday fo= r you. It is
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 almost ready right now, but I need to double-check
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 it before publishing.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Regards,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Andrew.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 On 8/17/23 20:03, Adam Hassick wrote:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Hi Andrew,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I'm adding the CI mailing list to thi= s
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 conversation. Others in the community might find
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 this conversation valuable.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 We do want to run testing on a regular basis. The
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Jenkins integration will be very useful for us, as
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 most of our CI is orchestrated by Jenkins.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I've conferred with the rest of the team, and we
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 think it would be best to move forward with mainly
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 option B.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 If you would like to know anything about our
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 testbeds that would help you with creating an
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 example ts-rigs repo, I'd be happy to answer any
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 questions you have.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 We have multiple test rigs (we call these
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "DUT-tester pairs") that we run= our existing
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hardware testing on, with differing network
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 hardware and CPU architecture. I figured this might
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 be an important detail.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Thanks,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Adam

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 On Thu, Aug 17, 2023 at 11:44=E2=80=AFAM = Andrew Rybchenko
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <andrew.rybchenko@oktetlabs.ru
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <mailto:andrew.rybchenko@oktetlabs.ru>> wrote:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Greatings Adam,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I'm happy to = hear that you're trying to bring
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 it up.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 As I understand t= he final goal is to run it on
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 regular basis. So= , we need to make it properly
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 from the very beg= inning.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Bring up of all f= eatures consists of 4 steps:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 1. Create site-sp= ecific repository (we call it
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ts-rigs) which co= ntains information about test
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 rigs and other si= te-specific information like
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 where to send mai= ls, where to store logs etc.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 It is required fo= r manual execution as well,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 since test rigs d= escription is essential. I'll
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 return to the top= ic below.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2. Setup logs sto= rage for automated runs.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Basically it is a= disk space plus apache2 web
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 server with few C= GI scripts which help a lot to
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 save disk space.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 3. Setup Bublik w= eb application which provides
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 web interface to = view testing results. Same as
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 https://ts-factory.io/bublik
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <https://ts-factory.io/bublik&= gt;

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 4. Setup Jenkins = to run tests on regularly,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 save logs in log = storage (2) and import it to
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 bublik (3).

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Last few month we= spent on our homework to make
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 it simpler to bri= ng up automated execution
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 using Jenkins -
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 https://github.com/ts-factory/te-jenkins
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <https://github.com/ts-factory/te-jenkins>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Corresponding bit= s in dpdk-ethdev-ts will be
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 available tomorro= w.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Let's return = to the step (1).

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Unfortunately the= re is no publicly available
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 example of the ts= -rigs repository since
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 sensitive site-sp= ecific information is located
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 there. But I'= m ready to help you to create it
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 for UNH. I see tw= o options here:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (A) I'll ask = questions and based on your
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 answers will crea= te the first draft with my
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 comments.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (B) I'll make= a template/example ts-rigs repo,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 publish it and yo= u'll create UNH ts-rigs based
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 on it.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Of course, I'= ll help to debug and finally bring
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 it up in any case= .

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 (A) is a bit simp= ler for me and you, but (B) is
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 a bit more generi= c and will help other
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 potential users t= o bring it up.
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 We can combine (A= )+(B). I.e. start from (A).
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 What do you think= ?

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Thanks,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Andrew.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 On 8/17/23 15:18,= Konstantin Ushakov wrote:
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 Greetings Adam,


=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Thanks for contac= ting us. I copy Andrew who
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 would be happy to= help

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Thanks,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Konstantin

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 On 16 Aug 2023, at 21:50, Adam Hassick
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <ahassick@iol.unh.edu>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0
<mailto:ahassick@iol.unh.edu> wrote:

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =EF=BB=BF
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Greetings Kons= tantin,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I am in the pr= ocess of setting up the DPDK
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Poll Mode Driv= er test suite as an addition to
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 our testing co= verage for DPDK at the UNH lab.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I have some qu= estions about how to set the
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 test suite arg= uments.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I have been ab= le to configure the Test Engine
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 to connect to = the hosts in the testbed. The
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 RCF, Configura= tor, and Tester all begin to
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 run, however t= he prelude of the test suite
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 fails to run.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 https://ts-factory.io/doc/dpdk-e= thdev-ts/index.html#test-parameters <https://ts-factory.io/doc/dpdk-ethdev-ts/index.h= tml#test-parameters>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The documentat= ion mentions that there are
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 several test p= arameters for the test suite,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 like for the I= UT test link MAC, etc. These
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 seem like they= would need to be set somewhere
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 to run many of= the tests.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I see in the T= est Engine documentation, there
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 are instructio= ns on how to create new
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 parameters for= test suites in the Tester
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 configuration,= but there is nothing in the
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 user guide or = in the Tester guide for how to
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 set the argume= nts for the parameters when
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 running the te= st suite that I can find. I'm
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 not sure if I = need to write my own Tester
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 config, or if = I should be setting these in
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 some other way= .

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 How should the= se values be set?

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I'm also n= ot sure what environment
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 variables/argu= ments are strictly necessary or
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 which are opti= onal.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Regards,
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Adam

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- =C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 *Adam Hassick*
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Senior Develop= er
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 UNH InterOpera= bility Lab
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ahassick@iol.unh.edu
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <mailto:ahassick@iol.unh.edu>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 iol.unh.edu = <https://www.iol.unh.edu/>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +1 (603) 475-8= 248



=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 *Adam Hassick*
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Senior Developer
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 UNH InterOperability Lab
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ahassick@iol.unh.edu &= lt;mailto:ahassick@iol.unh.edu>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 iol.unh.edu <= https://www.iol.unh.edu/>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +1 (603) 475-8248




=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 -- =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 *= Adam Hassick*
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 Senior Developer
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 UNH InterOperability Lab
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 ahassick@iol.= unh.edu <m= ailto:ahassick@iol.unh.edu>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 iol.unh.edu <https://www.iol.unh.ed= u/>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 +1 (603) 475-8248



=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 -- =C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 *Adam Hassick*
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Senior Developer
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 UNH InterOperability= Lab
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ahassick@iol.unh.edu <m= ailto:ahassick@iol.unh.edu>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 iol.unh.edu <https://www.iol.unh.edu/>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 +1 (603) 475-8248



=C2=A0=C2=A0=C2=A0 -- =C2=A0=C2=A0=C2=A0 *Adam Hassick*
=C2=A0=C2=A0=C2=A0 Senior Developer
=C2=A0=C2=A0=C2=A0 UNH InterOperability Lab
=C2=A0=C2=A0=C2=A0 ahassick@iol.unh.edu <mailto:ahassick@iol.unh.edu>
=C2=A0=C2=A0=C2=A0 iol.unh.edu &= lt;https://www.iol.unh.edu/>
=C2=A0=C2=A0=C2=A0 +1 (603) 475-8248



--=C2=A0
*Adam Hassick*
Senior Developer
UNH InterOperability Lab
ahassick@= iol.unh.edu &= lt;mailto:ahassick@iol.unh.edu>
iol.unh.edu <https://www.iol.un= h.edu/>
+1 (603) 475-8248




--
Adam Hassick
Senior Developer
UNH InterOperability Lab
+1 (603) 475-8248
--0000000000004660700603bfd6d9--