From: David Marchand <david.marchand@redhat.com>
To: Brandon Lo <blo@iol.unh.edu>
Cc: Lincoln Lavoie <lylavoie@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 10:02:01 +0200 [thread overview]
Message-ID: <CAJFAV8yqWL07fhX7fbNmxmKUrvRSaBhSTFfCOmfJqGsW9_fe4w@mail.gmail.com> (raw)
In-Reply-To: <CAOeXdvY1T-fd+OHT9bhZp1YPmeu_4NDbg1jzDypUcrQa0odakA@mail.gmail.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
next prev parent reply other threads:[~2021-06-10 8:02 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 [this message]
2021-06-10 8:13 ` Lincoln Lavoie
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=CAJFAV8yqWL07fhX7fbNmxmKUrvRSaBhSTFfCOmfJqGsW9_fe4w@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dodji@redhat.com \
--cc=dpdklab@iol.unh.edu \
--cc=lylavoie@iol.unh.edu \
--cc=mdr@ashroe.eu \
--cc=thomas@monjalon.net \
/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).