Meson buildtype for ci jobs?

[Patrick Robb <probb@iol.unh.edu>]

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

Hello all,

The lab recently received a request to re-enable Alpine compile jobs, which
have been disabled for almost a year. In dry running the compile job, I
noticed that it was failing. At the same time, David Marchand did an Alpine
compile with Github Actions which was successful. It seems the source of
the different behavior is the meson buildtype being used - the build script
used by GHA sets meson buildtype to debugoptimized, whereas the script used
by the community lab runs with buildtype debug (the meson default). I did
my own Github Actions runs (with both buildtype options) to sanity check:
https://github.com/PatrickRobbIOL/dpdk/actions/runs/4427160204/jobs/7764368640

The reason I'm writing this email is that I'm wondering whether the
buildtype decision made by those who wrote .ci/linux-build.sh for GHA was
intentional and important. I know many of the people who have commits on
that script follow this mailing list. Obviously if it's in some way more
appropriate for CI purposes to run meson setup in this way, I'm happy to
make that change at the lab and in the process that would free up bringing
Alpine compile testing online. But, if not, then I think it's most
appropriate to consider compile on Alpine as broken and avoid bringing
coverage for Alpine online until that issue is resolved.

Any thoughts on the matter are appreciated!

Best,
Patrick

-- 

Patrick Robb

Technical Service Manager

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

www.iol.unh.edu

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