From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 588] Setup ABI testing to run in UNH-IOL Community Lab
Date: Thu, 03 Dec 2020 19:54:11 +0000 [thread overview]
Message-ID: <bug-588-149@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=588
Bug ID: 588
Summary: Setup ABI testing to run in UNH-IOL Community Lab
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: ---
Per discussion on December 3 Community CI meeting, setup ABI testing to run as
part of the community lab compile tests.
Runs on top of compile tests, i.e. doesn’t need dedicated hardware. This
compares an ABI dump to the previous release, using libabigail. Need to store
the reference output from the previous release. Should be reported as a
separate check/test in patchworks, if possible (need to verify if this can be
easily done and wouldn’t double the number of reports for the compile runs).
Need to create a bug ticket for this. Travis's ABI check:
https://github.com/DPDK/dpdk/blob/main/.ci/linux-build.sh#L60
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-12-03 19:54 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-588-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).