From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 408] Add Arm hardware to the lab for general testing
Date: Tue, 25 Feb 2020 16:38:12 +0000 [thread overview]
Message-ID: <bug-408-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=408
Bug ID: 408
Summary: Add Arm hardware to the lab for general testing
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: UNH infra
Assignee: ci@dpdk.org
Reporter: jplsek@iol.unh.edu
CC: jplsek@iol.unh.edu
Target Milestone: ---
This hardware will also be paired with some nics to do extra testing with dts.
Recent email discussions:
We were waiting for the discussions in governing/tech boards to complete to
ship the hardware to the lab. We have started working with Ampere to
procure/configure/ship the servers to the lab. [...]
[...] run compilation, functional, functional-performance (such as rte ring
performance or rte_hash performance), DTS and performance tests. I am aware
that there are OVS tests being run as well, we would like to run them as well.
Essentially, all that is tested on x86 in UNH lab needs to be tested for Arm
platforms too. [...]
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-02-25 16:38 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=bug-408-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@dpdk.org \
/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).