DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Tal Shnaiderman <talshn@mellanox.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] DPDK Failing compilation on Windows
Date: Tue, 28 Apr 2020 16:18:16 -0400	[thread overview]
Message-ID: <CAOeXdvba0afA7gEKRotRqCPLqZN74b=_V8dzPzj4Yq-QsZgBVw@mail.gmail.com> (raw)
In-Reply-To: <AM0PR05MB5313BC1640D21C3FFD040A13A9AE0@AM0PR05MB5313.eurprd05.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 937 bytes --]

Hi Tal,

I think the more recent patches are not failing anymore due to your fix.
I will continue to keep an eye on it to make sure it's not failing on
Windows.

Thanks for letting us know,
Brandon

On Sun, Apr 26, 2020 at 8:48 AM Tal Shnaiderman <talshn@mellanox.com> wrote:

> Hi community lab,
>
>
>
> I’m writing to you regarding an issue I saw in DPDK patchwork.
>
>
>
> I submitted a fix for the Windows build test in
> https://patches.dpdk.org/patch/69036/
>
>
>
> However I noticed the later patches still get the build break error, e.g:
>
>
>
> http://mails.dpdk.org/archives/test-report/2020-April/128143.html
>
>
>
> Is the build still failing or did community lab not fetch the latest
> master branch?
>
>
>
> Thanks,
>
>
>
> Tal
>
>
>


-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

[-- Attachment #2: Type: text/html, Size: 3442 bytes --]

      reply	other threads:[~2020-04-28 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-26 12:47 Tal Shnaiderman
2020-04-28 20:18 ` Brandon Lo [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='CAOeXdvba0afA7gEKRotRqCPLqZN74b=_V8dzPzj4Yq-QsZgBVw@mail.gmail.com' \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=talshn@mellanox.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).