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 8820F45751; Tue, 6 Aug 2024 18:47:52 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5785540A89; Tue, 6 Aug 2024 18:47:52 +0200 (CEST) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mails.dpdk.org (Postfix) with ESMTP id 623E440270 for ; Tue, 6 Aug 2024 18:47:51 +0200 (CEST) Received: by linux.microsoft.com (Postfix, from userid 1086) id 8871820B7165; Tue, 6 Aug 2024 09:47:50 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 8871820B7165 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1722962870; bh=GaRtICUAt287LGxRTxvh7CVH2CwebK2BQ3FCqd5V+uI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=HiLfXgXniCoDmGLlrpikk8igl7Y84+X6No9RYUQVpRQtK/KisHHH7iRjEboHtXE4b QuGOqdrtryiWub1wu865HZZ7PQtP5I5gCDZEUbM9cWbQvZw55Tho8Aqr388mE4fPgQ iHlFW6c2f4l8ZaTCry00q//7+5pXfQcat6lvek6M= Date: Tue, 6 Aug 2024 09:47:50 -0700 From: Tyler Retzlaff To: Patrick Robb Cc: ci@dpdk.org, Stephen Hemminger Subject: Re: Windows Server 2019 in UNH CI Testing? Message-ID: <20240806164750.GA17212@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20240806054304.GB19300@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 Tue, Aug 06, 2024 at 12:38:32PM -0400, Patrick Robb wrote: > On Tue, Aug 6, 2024 at 1:43???AM Tyler Retzlaff > wrote: > > i don't see a lot of utility in maintaining the server 2019 any further. > > i think it is fine to consolidate and use the server 2022 vm. > > > > we will want to maintain the build with all 3 toolchains (which i think > > is what we already have on the 2022 setup?) and continue running the unit > > tests for the llvm/clang build (and mingw if we already do?) > > > > Okay, thanks Stephen and Tyler. We will discontinue usage of the > server 2019 VM, and run the 3 toolchains from serve 2022. somewhat related when you have time in your schedule i think you can also upgrade the compiler on the server 2022 vm to visual studio 17.10.x. the non-preview / release version of the compiler now contains everything needed for msvc + dpdk. ty