From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |WARNING| [GIT MASTER] 0f80c13b4d589f63a8ede56bea0a443750bdcc47
Date: Thu, 4 Aug 2022 05:42:46 +0000 (UTC) [thread overview]
Message-ID: <20220804054246.52690600E7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4848 bytes --]
_Testing issues_
Branch: tags/v21.11
0f80c13b4d589f63a8ede56bea0a443750bdcc47 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS | FAIL |
+---------------------+--------------------+----------------------+
| Fedora 31 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL 7 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 18.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 32 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Arch Linux | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 33 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 clang | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for Windows Server 2019 (dpdk_mingw64_compile): ====
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.2-rc1
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 objdump found: YES (C:\mingw64\mingw64\bin\objdump.EXE)
Program python3 found: YES (c:\python38\python.exe)
Program more found: YES (C:\Windows\system32\more.COM)
Checking for size of "void *" : 8
Checking for size of "void *" : 8
Library m found: YES
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Arch Linux
Kernel: 5.4.0-73-generic
Compiler: gcc 11.1.0
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/20961/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-08-04 5:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 5:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-08 5:48 dpdklab
2022-08-07 5:51 dpdklab
2022-08-06 5:51 dpdklab
2022-08-05 6:05 dpdklab
2022-08-04 6:07 dpdklab
2022-08-03 6:05 dpdklab
2022-08-02 6:13 dpdklab
2022-08-01 6:14 dpdklab
2022-07-31 5:54 dpdklab
2022-07-30 6:04 dpdklab
2022-07-29 6:18 dpdklab
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=20220804054246.52690600E7@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.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).