From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B49DB41EA1 for ; Wed, 15 Mar 2023 17:08:13 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B01F840A7A; Wed, 15 Mar 2023 17:08:13 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 0B64F40141 for ; Wed, 15 Mar 2023 17:08:11 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678896491; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=x/vPG6yCyLnXUOKYxEHxjvHV6vGgL9noiEaUGL9Xyiw=; b=P9yw8GgALMa5C30+XXh0bH2HgO3ZrdRudDKLGpS/1Bu7XcPSOSmnvdQ1lAsPOd+rpthjl5 6ZtZdhZdiRK6WgfUU5v+DtlB2Lj6hxBSwQ99LATfIfiiMhB5Z+i26g065okxds5mKkul71 YuQybz9R+37T8QFkQ5YWlucE/GzVcNg= Received: from mail-pf1-f200.google.com (mail-pf1-f200.google.com [209.85.210.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-8-qVTd4MP-Of63gxuwdoUrfA-1; Wed, 15 Mar 2023 12:08:10 -0400 X-MC-Unique: qVTd4MP-Of63gxuwdoUrfA-1 Received: by mail-pf1-f200.google.com with SMTP id i7-20020a626d07000000b005d29737db06so10380287pfc.15 for ; Wed, 15 Mar 2023 09:08:10 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678896489; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=x/vPG6yCyLnXUOKYxEHxjvHV6vGgL9noiEaUGL9Xyiw=; b=WUNCMAFyG/hoaKckPc5nq2jyQJWO6URIfTMJNmSBdkwPBfsqSuEzJeeeuFZypoT+zI +gTxO373e/hqdqa/rz/pmRtDZcFfQWpV+oadKiuaSSBztFcakk7Og5uJzSIlBgXdaDbH tLQHsspxLWHHU7HkaRg3+stEawP2WKvl4EKIArts0TwImydvPFQu71cVniCniXHeg7cc 5l9EALEbm1QteucJ26EFJkak4detaq/GtlGQAmJediluCRNW4PK0gjKlA/VgLr2lqvVT rmY4H1HVoLyPRV1fIYKsGD3NLGcqhWHePTvtri1PFZJroLc5/7XrWbXZzctVpHhWWpT3 7xWA== X-Gm-Message-State: AO0yUKXU4RwF7tRm+OAC5/G2fg97DsmteLrbZnTHTD5fPR7EwP9K/Fv0 My6wDAlIeWKg67AKSN5nOzMoH78YvBZudapZYS5Q4wZ6vA3E5AZNiHkgrbTztaAg3W+rdxcUnUY Oj+uDVp1jB1UyKMmVUA== X-Received: by 2002:a17:902:dac9:b0:19f:87b5:186d with SMTP id q9-20020a170902dac900b0019f87b5186dmr19583plx.9.1678896489127; Wed, 15 Mar 2023 09:08:09 -0700 (PDT) X-Google-Smtp-Source: AK7set872jvznNoTDPKyzgyUdjB5ZA7lw7nj1a0O5ZQDo9LInW2TZPFx8ZqeZO7Ll3nlstwdSSFM5nA03cvPwVKrXjk= X-Received: by 2002:a17:902:dac9:b0:19f:87b5:186d with SMTP id q9-20020a170902dac900b0019f87b5186dmr19570plx.9.1678896488657; Wed, 15 Mar 2023 09:08:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 15 Mar 2023 17:07:56 +0100 Message-ID: Subject: Re: Meson buildtype for ci jobs? To: Patrick Robb Cc: ci@dpdk.org, Aaron Conole , Bruce Richardson , Thomas Monjalon X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org On Wed, Mar 15, 2023 at 4:52=E2=80=AFPM Patrick Robb wr= ote: > > Hello all, > > The lab recently received a request to re-enable Alpine compile jobs, whi= ch 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 t= he 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: h= ttps://github.com/PatrickRobbIOL/dpdk/actions/runs/4427160204/jobs/77643686= 40 Are you sure about the default value? Afaics, meson selects by default a "release" buildtype (and I think I always saw this value in the past). I have this with meson 1.0. $ meson setup qsdlgfh ... $ meson configure qsdlgfh | grep buildtype buildtype release [plain, debug, debugoptimized, Build type to use > > The reason I'm writing this email is that I'm wondering whether the build= type decision made by those who wrote .ci/linux-build.sh for GHA was intent= ional and important. I know many of the people who have commits on that scr= ipt follow this mailing list. Obviously if it's in some way more appropriat= e for CI purposes to run meson setup in this way, I'm happy to make that ch= ange at the lab and in the process that would free up bringing Alpine compi= le testing online. But, if not, then I think it's most appropriate to consi= der compile on Alpine as broken and avoid bringing coverage for Alpine onli= ne until that issue is resolved. The reason why we went with debugoptimized was primarly for the ABI checks, as by default, the debug symbols were missing (which would match with a "release" default buildtype). See 777014e56d07 ("devtools: add ABI checks"). --=20 David Marchand