DPDK CI discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dpdklab <dpdklab@iol.unh.edu>
Cc: ci@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>,
	Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-ci] |FAILURE| pw102710-102718 [PATCH] [v6, 9/9] interrupts: extend event list
Date: Mon, 25 Oct 2021 09:07:04 +0200	[thread overview]
Message-ID: <CAJFAV8xTf9nuSd8SmesN5n_2WKhpWCkGDwcTHktTX7NoGJOcRQ@mail.gmail.com> (raw)
In-Reply-To: <20211025060328.976FA60524@noxus.dpdklab.iol.unh.edu>

On Mon, Oct 25, 2021 at 8:03 AM <dpdklab@iol.unh.edu> wrote:
>
> Test-Label: iol-x86_64-compile-testing
> Test-Status: FAILURE
> http://dpdk.org/patch/102718
>
> _Testing issues_
>
> Submitter: David Marchand <david.marchand@redhat.com>
> Date: Sunday, October 24 2021 20:04:49
> DPDK git baseline: Repo:dpdk
>   Branch: master
>   CommitID:daa02b5cddbb8e11b31d41e2bf7bb1ae64dcae2f
>
> 102710-102718 --> testing fail
>
> Test environment and result as below:
>
> +---------------------+--------------------+----------------------+-------------------+
> |     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_compile_spdk |
> +=====================+====================+======================+===================+
> | Windows Server 2019 | PASS               | FAIL                 | SKIPPED           |

I triggered a rebuild on this series, since the first run got me a
rather empty log.
On the second run, I get the same output (from log.txt, the only file
in test archive):

The Meson build system
Version: 0.57.1
Source dir: C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Mingw64\dpdk
Build dir: C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Mingw64\dpdk\build
Build type: native build
Program more found: YES (C:\Windows\system32\more.COM)
Project name: DPDK
Project version: 21.11.0-rc0
C compiler for the host machine: gcc (gcc 8.1.0 "gcc
(x86_64-posix-seh-rev0, Built by MinGW-W64 project) 8.1.0")
C linker for the host machine: gcc ld.bfd 2.30
Host machine cpu family: x86_64
Host machine cpu: x86_64
Message: ## Building in Developer Mode ##
Program pkg-config pkgconf found: NO
Program check-symbols.sh found: YES (sh
C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Mingw64\dpdk\buildtools\check-symbols.sh)
Program options-ibverbs-static.sh found: YES (sh
C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Mingw64\dpdk\buildtools\options-ibverbs-static.sh)
Program binutils-avx512-check.sh found: YES (sh
C:\Users\builder\jenkins\workspace\Windows-Compile-DPDK-Mingw64\dpdk\buildtools\binutils-avx512-check.sh)
Program python3 found: YES (c:\python38\python.exe)
Program more found: YES (C:\Windows\system32\more.COM)


I ran mingw compilation as part of my own checks, so I think mingw
compilation is fine.
I'll ignore this report for now.
Can you look at it when you get a chance?


Thanks.


-- 
David Marchand


       reply	other threads:[~2021-10-25  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211025060328.976FA60524@noxus.dpdklab.iol.unh.edu>
2021-10-25  7:07 ` David Marchand [this message]
2021-10-25 12:25   ` Lincoln Lavoie

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=CAJFAV8xTf9nuSd8SmesN5n_2WKhpWCkGDwcTHktTX7NoGJOcRQ@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=lylavoie@iol.unh.edu \
    /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).