DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 598] check ABI compatibility per patch
Date: Wed, 09 Dec 2020 09:19:39 +0000	[thread overview]
Message-ID: <bug-598-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=598

            Bug ID: 598
           Summary: check ABI compatibility per patch
           Product: lab
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: High
         Component: job scripts
          Assignee: ci@dpdk.org
          Reporter: thomas@monjalon.net
                CC: david.marchand@redhat.com, dpdklab@iol.unh.edu
  Target Milestone: ---

Please enable ABI check as part of the compilation job.

This is described in the documentation:
http://doc.dpdk.org/guides/contributing/patches.html#checking-abi-compatibility

The environment variable DPDK_ABI_REF_VERSION must be set to v20.11
during 21.02 cycle.
Then when 21.02 will be released, it should be updated to v21.02,
and so on at each new release.

If compilation is tested with the script devtools/test-meson-builds.sh
then the ABI will be automatically checked.

The variable DPDK_ABI_REF_DIR must be set to the ABI reference cache
which can be built only once per release.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2020-12-09  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09  9:19 bugzilla [this message]
2020-12-17 21:24 ` 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-598-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).