DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	"Gal Cohen (ProdM)" <galco@nvidia.com>,
	 Adam Hassick <ahassick@iol.unh.edu>,
	ci@dpdk.org
Subject: TS-Factory ethdev testing on cx5
Date: Tue, 10 Oct 2023 10:21:08 -0400	[thread overview]
Message-ID: <CAJvnSUC4R+LwixiedHCd=POmnPep+Ni7d2y-P_hk_v3e8P4faA@mail.gmail.com> (raw)

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

Hi Ali,

As discussed in the CI meetings, one of the 2023 work items for the
Community Lab is to explore running the TS-Factory testing framework for
DPDK ethdev tests. Ideally this will greatly expand our test coverage in
the lab.

So, we have run this using cx5 nics on some dev servers and are happy with
the results. In production, we would run this on a periodic basis on as
much hardware as possible, and post the results to a page on the Community
Lab dashboard.

Now that we are happy with how the ts-factory runs on the cx5 NIC on dev
servers, the next step is to set it up on Nvidia's production servers here.
I would like to schedule a whole business day of downtime for the Nvidia
servers so that we can run the testing framework, check that the results
are as expected, then run DTS and verify there is no unexpected conflict,
etc.

Is this acceptable to you? If so, a Tuesday or Thursday would work best for
us. Would either this Thursday, or next Tuesday be fine?

Thanks,
Patrick

[-- Attachment #2: Type: text/html, Size: 1206 bytes --]

                 reply	other threads:[~2023-10-10 14:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJvnSUC4R+LwixiedHCd=POmnPep+Ni7d2y-P_hk_v3e8P4faA@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=ahassick@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=ci@dpdk.org \
    --cc=galco@nvidia.com \
    --cc=thomas@monjalon.net \
    /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).