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 D5E59A00C2; Wed, 23 Feb 2022 19:05:00 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9FEA840E5A; Wed, 23 Feb 2022 19:05:00 +0100 (CET) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mails.dpdk.org (Postfix) with ESMTP id 3532440DF6 for ; Wed, 23 Feb 2022 19:05:00 +0100 (CET) Received: by linux.microsoft.com (Postfix, from userid 1086) id 56A6D20C31CE; Wed, 23 Feb 2022 10:04:59 -0800 (PST) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 56A6D20C31CE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1645639499; bh=NZOqnhUll42AqTyk7RtszRi3cSGIG8JOEseaU/Uq/Ug=; h=Date:From:To:Subject:From; b=SN5wT52TCk1YlzxZui3rbFict1oVARdwDz0O33WsiQ6i7uOhz/0VS3AcZqVpEFlLg CgS0jYOLaRoXyr0c/j2Cg2blu9Q5GoKdmjNqDcyQ4hsEY91HSdeRpoMcOS6T82aDqC KtKpl0BNvE1sBLU89CVWbw2bn/8c1ylT7F/q5eO8= Date: Wed, 23 Feb 2022 10:04:59 -0800 From: Tyler Retzlaff To: dev@dpdk.org Subject: meson test --test-args="--no-huge" Message-ID: <20220223180459.GA31155@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org noticing that meson test --test-args="--no-huge" has a pretty significant number of failures. given --no-huge isn't tested at all is there value in keeping no-huge support? or is this just unintentional since the --no-huge configuration isn't run in the CI pipelines? what's the promise from dpdk for --no-huge? deprecated? supported?