<div dir="ltr"><div><div>Hi Andrew,<br><br></div><div>I'm adding the CI mailing list to this conversation. Others in the community might find this conversation valuable.<br></div><div><br></div>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.<br></div><div>I've conferred with the rest of the team, and we think it would be best to move forward with mainly option B.<br></div><div>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.<br></div><div><br></div><div>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.<br></div><div><br></div><div>Thanks,<br></div><div>Adam<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 17, 2023 at 11:44 AM Andrew Rybchenko <<a href="mailto:andrew.rybchenko@oktetlabs.ru">andrew.rybchenko@oktetlabs.ru</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>Greatings Adam,<br>
<br>
I'm happy to hear that you're trying to bring it up.<br>
<br>
As I understand the final goal is to run it on regular basis. So,
we need to make it properly from the very beginning.<br>
Bring up of all features consists of 4 steps:<br>
<br>
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.<br>
<br>
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.<br>
<br>
3. Setup Bublik web application which provides web interface to
view testing results. Same as <a href="https://ts-factory.io/bublik" target="_blank">https://ts-factory.io/bublik</a><br>
<br>
4. Setup Jenkins to run tests on regularly, save logs in log
storage (2) and import it to bublik (3).<br>
<br>
Last few month we spent on our homework to make it simpler to
bring up automated execution using Jenkins -
<a href="https://github.com/ts-factory/te-jenkins" target="_blank">https://github.com/ts-factory/te-jenkins</a><br>
Corresponding bits in dpdk-ethdev-ts will be available tomorrow.<br>
<br>
Let's return to the step (1).<br>
<br>
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:<br>
<br>
(A) I'll ask questions and based on your answers will create the
first draft with my comments.<br>
<br>
(B) I'll make a template/example ts-rigs repo, publish it and
you'll create UNH ts-rigs based on it.<br>
<br>
Of course, I'll help to debug and finally bring it up in any case.<br>
<br>
(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.<br>
We can combine (A)+(B). I.e. start from (A). What do you think?<br>
<br>
Thanks,<br>
Andrew.<br>
<br>
On 8/17/23 15:18, Konstantin Ushakov wrote:<br>
</div>
<blockquote type="cite">
Greetings Adam,
<div><br>
</div>
<div><br>
</div>
<div>Thanks for contacting us. I copy Andrew who would be happy to
help<br>
<br>
<div dir="ltr">Thanks,
<div>Konstantin</div>
</div>
<div dir="ltr"><br>
<blockquote type="cite">On 16 Aug 2023, at 21:50, Adam Hassick
<a href="mailto:ahassick@iol.unh.edu" target="_blank"><ahassick@iol.unh.edu></a> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>
<div>
<div>
<div>Greetings Konstantin,<br>
<br>
</div>
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.<br>
<br>
</div>
I have some questions about how to set the test suite
arguments.<br>
<br>
</div>
<div>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.<br>
</div>
<div><br>
<a href="https://ts-factory.io/doc/dpdk-ethdev-ts/index.html#test-parameters" target="_blank">https://ts-factory.io/doc/dpdk-ethdev-ts/index.html#test-parameters</a><br>
<br>
</div>
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.<br>
<br>
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.<br>
<br>
How should these values be set?<br>
<br>
</div>
<div>I'm also not sure what environment
variables/arguments are strictly necessary or which are
optional.<br>
</div>
<div><br>
</div>
<div>Regards,<br>
</div>
<div>Adam<br>
</div>
<div>
<div>
<div>
<div>
<div>
<div><br>
<span class="gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>
<div><b><span style="background-color:rgb(255,255,255)"><span style="color:rgb(102,102,102)">Adam
Hassick</span></span></b><br>
</div>
<span style="color:rgb(102,102,102)"></span></div>
<div><span style="color:rgb(102,102,102)">Senior
Developer</span></div>
<div><span style="color:rgb(102,102,102)"><span style="color:rgb(11,83,148)"><span style="background-color:rgb(255,255,255)">UNH
InterOperability Lab</span></span></span><span style="color:rgb(102,102,102)"></span></div>
<div><span style="color:rgb(102,102,102)"><a href="mailto:ahassick@iol.unh.edu" target="_blank">ahassick@iol.unh.edu</a><br>
</span></div>
<div><span style="color:rgb(102,102,102)"><a href="https://www.iol.unh.edu/" target="_blank">iol.unh.edu</a><br>
</span></div>
+1 (603) 475-8248<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div><b><span style="background-color:rgb(255,255,255)"><span style="color:rgb(102,102,102)">Adam Hassick</span></span></b><br></div><span style="color:rgb(102,102,102)"></span></div><div><span style="color:rgb(102,102,102)">Senior Developer</span></div><div><span style="color:rgb(102,102,102)"><span style="color:rgb(11,83,148)"><span style="background-color:rgb(255,255,255)">UNH InterOperability Lab</span></span></span><span style="color:rgb(102,102,102)"></span></div><div><span style="color:rgb(102,102,102)"><a href="mailto:ahassick@iol.unh.edu" target="_blank">ahassick@iol.unh.edu</a><br></span></div><div><span style="color:rgb(102,102,102)"><a href="https://www.iol.unh.edu/" target="_blank">iol.unh.edu</a><br></span></div>+1 (603) 475-8248<br></div></div>