From: Patrick Robb <probb@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>,
dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
ci@dpdk.org
Subject: Re: [PATCH 0/2] build eal & ring libraries with MSVC
Date: Wed, 6 Mar 2024 09:48:42 -0500 [thread overview]
Message-ID: <CAJvnSUCrWusuuYd0-JUjDONjqY3cbu1brLC-mW4kN1eF9ACdbA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8wTZ-4OCnKqsHoJUn=dHeK8fpQ3KGyeOBGaCHjUco=a8g@mail.gmail.com>
On Wed, Mar 6, 2024 at 5:00 AM David Marchand <david.marchand@redhat.com> wrote:
>
> On Tue, Feb 27, 2024 at 8:22 PM Tyler Retzlaff
> <roretzla@linux.microsoft.com> wrote:
> >
> > Enable build of eal & ring library when building with MSVC.
> >
> > This series depends on 2 other series that seem to be near being
> > accepted for merge.
> >
> > https://patches.dpdk.org/project/dpdk/list/?series=31229
> > https://patches.dpdk.org/project/dpdk/list/?series=31230
> >
> > Since the rc2 deadline is soon this series is being submitted now
> > to solicit feedback. The CI is expected to fail without the above
> > series being merged.
> >
>
> Series applied, thanks Tyler.
>
> Btw, I noticed a failure in UNH for MSVC, but it is not reported as
> such in patchwork.
> https://lab.dpdk.org/results/dashboard/patchsets/29302/
> https://patchwork.dpdk.org/project/dpdk/patch/1709061720-4843-3-git-send-email-roretzla@linux.microsoft.com/
>
> Is there something to change in how UNH reports for the MSVC job?
Hi David,
There was a discussion about this on Slack in the infra-issues space.
You can see the correct test report here:
https://inbox.dpdk.org/test-report/65deb584.d40a0220.71354.9933SMTPIN_ADDED_MISSING@mx.google.com/
Which at the time of the discussion was the latest update for the
iol-compile-amd64-testing context sent to patchwork. So this appears
to be an anomaly.
>
>
> --
> David Marchand
>
prev parent reply other threads:[~2024-03-06 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 19:21 Tyler Retzlaff
2024-02-27 19:21 ` [PATCH 1/2] build: build eal library " Tyler Retzlaff
2024-02-27 19:22 ` [PATCH 2/2] build: build ring " Tyler Retzlaff
2024-02-28 9:07 ` [PATCH 0/2] build eal & ring libraries " Bruce Richardson
2024-03-06 10:00 ` David Marchand
2024-03-06 14:48 ` 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=CAJvnSUCrWusuuYd0-JUjDONjqY3cbu1brLC-mW4kN1eF9ACdbA@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
/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).