From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 243] DPDK Compilation Coverage
Date: Tue, 09 Apr 2019 14:09:12 +0000 [thread overview]
Message-ID: <bug-243-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=243
Bug ID: 243
Summary: DPDK Compilation Coverage
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: UNH infra
Assignee: ci@dpdk.org
Reporter: jplsek@iol.unh.edu
CC: jplsek@iol.unh.edu
Target Milestone: ---
It was discussed to add more compilation coverage between labs for DPDK.
This involves compiling based on operating system/distribution, CPU
architecture, and possibly the build system.
Results will be posted to patchwork.
We need some type of matrix of what operating systems that we want to be
supported, along with dependencies and build arguments. This will evolve over
time.
Some labs will have unique build systems, and some will overlap, which is fine.
This matrix should preferably be done before July, as that is also when the
UNH-IOL will have a larger VM infrastructure to create these build systems.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-04-09 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 14:09 bugzilla [this message]
2019-11-19 19:09 ` bugzilla
2020-04-21 14:25 ` bugzilla
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-243-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).