* [dpdk-stable] DPDK LTS Release Build-Testing miss - let us try to improve
@ 2021-03-26 7:54 Christian Ehrhardt
0 siblings, 0 replies; only message in thread
From: Christian Ehrhardt @ 2021-03-26 7:54 UTC (permalink / raw)
To: John McNamara; +Cc: Luca Boccassi, dpdk stable
I still owe you a summary of how the recent issue we discussed in the
Release meeting yesterday and how it could be catched better in the
#1 The Issue (skipping over most technical details intentionally)
There were linking changes that crept into DPDK 19.11.x and various
companies (including myself) have tested their software against it
successfully which led to the release of 19.11. as they are. But
later on it was found that rebuilding the dpdk-consuming software (in
this case OpenVswitch) no longer works with the new releases - and
thereby we have broken software that depends on us in stable releases.
#2 Solution - rebuild DPDK depending SW as part of the verification process
The Tests that are done for the verification of DPDK stable releases
should not only cover "running software against it" but also
"(re-)bulding software against it. Here we have a slight issue, as in
the current example newer openvswitch 2.14.x and 2.15.x work fine with
the new and the old code. But OVS 2.13.x which is their LTS stream and
the one that timewise came together with 19.11 is the one that breaks.
#3 Better Solution - rebuild (also old) DPDK depending SW as part of
the verification process
We should not only ask to "(re-)build the SW against the new DPDK" but
also to "(re-)build the SW level that matches the given DPDK release".
In this particular case for e.g. DPDK 19.11.x releases we'd always
expect to also have OVS 2.13 to be tried against it. In a similar
fashion DPDK 20.11 will always have to be tested vs OVS 2.15 even if
in a year there might be a newer OVS revision.
It would be great if you could sort that out with all associated
Test/Verification and Openvswitch peers that are involved with the
project. Once you feel that it was thoroughly cleared I would tag
19.11.8-rc1 as suggested by Thomas in the call. On that we can check
if the tests are done and also include a convincing amount of "and yes
my SW still rebuilds fine against the new release".
Thanks in advance!
Staff Engineer, Ubuntu Server
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-03-26 7:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-26 7:54 [dpdk-stable] DPDK LTS Release Build-Testing miss - let us try to improve Christian Ehrhardt
patches for DPDK stable branches
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://inbox.dpdk.org/stable/0 stable/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 stable stable/ http://inbox.dpdk.org/stable \
Example config snippet for mirrors.
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git