From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Huichao Cai <chcchc88@163.com>
Subject: |WARNING| pw104643 [PATCH] test/ipfrag: check fragment IPv4 header options
Date: Wed, 24 Nov 2021 02:57:42 -0500 (EST) [thread overview]
Message-ID: <20211124075742.470E560524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 5529 bytes --]
Test-Label: iol-x86_64-compile-testing
Test-Status: WARNING
http://dpdk.org/patch/104643
_Testing issues_
Submitter: Huichao Cai <chcchc88@163.com>
Date: Wednesday, November 24 2021 07:00:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0c6e27549c03695f85d949f5195a166b449b419c
104643 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS | FAIL |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 18.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 31 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 32 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL 7 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Arch Linux | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 33 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | 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.0-rc3
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 9.0 and gcc 8.1.0 (MinGW)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
CentOS 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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)
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 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
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/patchsets/20346/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2021-11-24 7:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211124075742.470E560524@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=chcchc88@163.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.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).