DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Brandon Lo <blo@iol.unh.edu>, dpdklab <dpdklab@iol.unh.edu>,
	ci@dpdk.org,  Aaron Conole <aconole@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Ray Kinsella <mdr@ashroe.eu>, Dodji Seketeli <dodji@redhat.com>
Subject: Re: [dpdk-ci] [dpdklab] ABI test failing for openSUSE and Arch Linux
Date: Thu, 10 Jun 2021 04:13:07 -0400
Message-ID: <CAOE1vsOzcoEyNxx5kz--5a_33++C5mr_Z7og1heQc6GhqvA5PA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8yqWL07fhX7fbNmxmKUrvRSaBhSTFfCOmfJqGsW9_fe4w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]

Hi David,

I think yes.  What Brandon was referring to is linking the process we use
to refresh the container images and the rebuild of the ABI references, so
one triggers the other.  What happened with the failure was the
container images got rebuilt, and that pulled in updates that change the
ABI output (in valid ways), which then "look like" a failure or change from
the reference that was previously saved off.

We save off older versions of the container images (i.e. things are
tagged), so we can always roll back if need to.  ABI reference generation
should be deterministic on that container image, so we don't save
"versions" of those references.


On Thu, Jun 10, 2021 at 4:02 AM David Marchand <david.marchand@redhat.com>

> On Wed, Jun 9, 2021 at 5:07 PM Brandon Lo <blo@iol.unh.edu> wrote:
> > To streamline this entire process, we are working on a job or pipeline
> > to automate refreshing all of the images and recreate the ABI
> > references.
> I understand the motivation, but will we have a clear idea of which
> ABI reference has been used and how to reproduce its generation (sha1,
> toolchain, libc, libabigail and such packages versions, version of the
> script generating the reference) ?
> If something breaks later and we don't know clearly how/if a reference
> changed, it will be a pain to analyse.
> --
> David Marchand

*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
+1-603-674-2755 (m)

[-- Attachment #2: Type: text/html, Size: 3106 bytes --]

      reply	other threads:[~2021-06-10  8:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04  7:58 [dpdk-ci] " David Marchand
2021-06-04 13:52 ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
2021-06-04 14:02   ` David Marchand
2021-06-04 18:28     ` Owen Hilyard
2021-06-07  8:33   ` David Marchand
2021-06-09 15:07     ` Brandon Lo
2021-06-10  8:02       ` David Marchand
2021-06-10  8:13         ` Lincoln Lavoie [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAOE1vsOzcoEyNxx5kz--5a_33++C5mr_Z7og1heQc6GhqvA5PA@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dodji@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=mdr@ashroe.eu \
    --cc=thomas@monjalon.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ https://inbox.dpdk.org/ci \
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git