From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 706] 2021 Epic: Expand compile, unit testing, and ABI test coverage
Date: Mon, 17 May 2021 21:01:10 +0000 [thread overview]
Message-ID: <bug-706-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=706
Bug ID: 706
Summary: 2021 Epic: Expand compile, unit testing, and ABI test
coverage
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: UNH infra
Assignee: ci@dpdk.org
Reporter: lylavoie@iol.unh.edu
CC: dpdklab@iol.unh.edu
Target Milestone: ---
Summary: Expand the coverage in terms of OS and architectures for the compile,
unit, and ABI testing.
* Completed Q1 Story: Migrate all compile testing to containers, expect for
Windows and FreeBSD. OS Coverage: Ubuntu 20.04, Ubunutu 18.04, CentOS 8, CentOS
Stream 8, Fedora 31, Fedora 32, OpenSUSE Leap 15, Arch Linux (latest /
rolling), RHEL 7, RHEL 8
* Completed Q1 Story: Deploy ABI testing to all non-Windows test systems.
* Q1 Story: Deploy unit testing to run in each container.
* Q2 Story: Deploy Fedora 33 and Fedora 34 to containers for compile, unit, and
ABI testing.
* Q2 Story: Generate compilation profile reporting using gcov.
* Q2 Story: Deploy container for cross-compile testing (to aarch64 target).
* Q2 Story: Create VM for latest FreeBSD 13.0, deploy compile, unit, and ABI
testing.
* Q3 Story: Deploy Ubsan and asan for additional bug testing / reporting,
during unit testing.
* Q3 Story: Deploy container for ARM SVE2 unit testing.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-05-17 21:01 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-706-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).