From: Patrick Robb <probb@iol.unh.edu>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: ci@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
Jeremy Spewock <jspewock@iol.unh.edu>
Subject: Re: Windows Server 2019 in UNH CI Testing?
Date: Tue, 6 Aug 2024 13:10:25 -0400 [thread overview]
Message-ID: <CAJvnSUC9K0-FFOWnZ93rpnHUYj49wNkiQpHHO-6Sr=iAD2ncyg@mail.gmail.com> (raw)
In-Reply-To: <20240806164750.GA17212@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Tue, Aug 6, 2024 at 12:47 PM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
>
> On Tue, Aug 06, 2024 at 12:38:32PM -0400, Patrick Robb wrote:
> > On Tue, Aug 6, 2024 at 1:43???AM Tyler Retzlaff
> > <roretzla@linux.microsoft.com> 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
Perfect. For context, we are no longer on the Preview version (we did
an upgrade some months ago), but without checking I'm guessing there
is an even newer version available now. We will look.
prev parent reply other threads:[~2024-08-06 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 19:14 Patrick Robb
2024-07-25 21:53 ` Stephen Hemminger
2024-08-06 5:43 ` Tyler Retzlaff
2024-08-06 16:38 ` Patrick Robb
2024-08-06 16:47 ` Tyler Retzlaff
2024-08-06 17:10 ` Patrick Robb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJvnSUC9K0-FFOWnZ93rpnHUYj49wNkiQpHHO-6Sr=iAD2ncyg@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).