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 6C6C545746; Tue, 6 Aug 2024 07:43:07 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 63042402CF; Tue, 6 Aug 2024 07:43:07 +0200 (CEST) Received: from linux.microsoft.com (linux.microsoft.com [13.77.154.182]) by mails.dpdk.org (Postfix) with ESMTP id 843DC402BA for ; Tue, 6 Aug 2024 07:43:05 +0200 (CEST) Received: by linux.microsoft.com (Postfix, from userid 1086) id 933CB20B7165; Mon, 5 Aug 2024 22:43:04 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 linux.microsoft.com 933CB20B7165 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.microsoft.com; s=default; t=1722922984; bh=tCDOI9dc49y5YgsrqXY4VSette0Bzf5KAhVsT7YPVhY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=BtEjgL0PW7iNRTb63jGXuCv4Vgo1n9rgYXCY9VSR3COUJF2NXznWq48K5KcxunUzn 2/Nqu9L+Wfe3dKZVZJjEnQi2I22zR/hIDfPL9trF0ElhwRn4s2sKRb5cuS7OAjeVLW vz/9AyzH0hlu8ZCJ+ZcqGbKY9SXIduki7PuKAOVk= Date: Mon, 5 Aug 2024 22:43:04 -0700 From: Tyler Retzlaff To: Patrick Robb Cc: ci@dpdk.org, Stephen Hemminger Subject: Re: Windows Server 2019 in UNH CI Testing? Message-ID: <20240806054304.GB19300@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: 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 hi Patrick, On Thu, Jul 25, 2024 at 03:14:37PM -0400, Patrick Robb wrote: > Hello Tyler, > > Windows Server 2019 mainstream end of support date is January 2024, > and extended end of support date is January 2029. > > Currently at UNH we have two VMs (windows server 2019 and 2022) both > running the Clang-LLVM & MinGW-64 compile jobs. > > The server 2022 machine also runs the custom MSVC compile jobs that we > set up in Fall 2023. > > So, with Windows Server 2019 reaching end of regular support, should > we discontinue CI on this system, or maintain it until (potentially) > 2029 when it reaches end of extended support? 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?) ty > > I am okay with either, I just don't necessarily understand how > significant the regular vs extended support distinction is, and > whether the results from the older system are still valuable for > developers. > > Cheers. > > -Patrick > > https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019