automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw89062-89065 [PATCH] [v3, 4/4] net: replace Windows networking shim
Date: Sat, 13 Mar 2021 18:24:41 -0500 (EST)	[thread overview]
Message-ID: <20210313232441.2F17C19DA1@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/89065

_Testing issues_

Submitter: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Date: Saturday, March 13 2021 22:22:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1e28e842e08428ff5716fbe909bf5acd0365aaf6

89062-89065 --> testing fail

Test environment and result as below:

+---------------------+----------------------+--------------------+----------------+-------------------+
|     Environment     | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_unit_test | dpdk_compile_spdk |
+=====================+======================+====================+================+===================+
| Windows Server 2019 | FAIL                 | FAIL               | SKIPPED        | SKIPPED           |
+---------------------+----------------------+--------------------+----------------+-------------------+
| FreeBSD 11.2        | SKIPPED              | PASS               | SKIPPED        | SKIPPED           |
+---------------------+----------------------+--------------------+----------------+-------------------+
| CentOS 8            | SKIPPED              | PASS               | SKIPPED        | SKIPPED           |
+---------------------+----------------------+--------------------+----------------+-------------------+
| openSUSE Leap 15    | SKIPPED              | PASS               | SKIPPED        | SKIPPED           |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Arch Linux          | SKIPPED              | PASS               | SKIPPED        | SKIPPED           |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Fedora 31           | SKIPPED              | PASS               | SKIPPED        | PASS              |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Ubuntu 18.04 ARM    | SKIPPED              | PASS               | PASS           | SKIPPED           |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Fedora 32           | SKIPPED              | PASS               | SKIPPED        | SKIPPED           |
+---------------------+----------------------+--------------------+----------------+-------------------+
| Ubuntu 18.04        | SKIPPED              | PASS               | PASS           | PASS              |
+---------------------+----------------------+--------------------+----------------+-------------------+

==== 20 line log output for Windows Server 2019 (dpdk_mingw64_compile): ====
[IPPROTO_SCTP] = RTE_PTYPE_INNER_L4_SCTP,
^~~~~~~~~~~~
IPPROTO_TCP
../lib/librte_net/rte_net.c:120:4: error: array index in initializer not of integer type
../lib/librte_net/rte_net.c:120:4: note: (near initialization for 'ptype_inner_l4_proto')
../lib/librte_net/rte_net.c: In function 'ptype_tunnel':
../lib/librte_net/rte_net.c:132:7: error: 'IPPROTO_GRE' undeclared (first use in this function); did you mean 'IPPROTO_GGP'?
case IPPROTO_GRE: {
^~~~~~~~~~~
IPPROTO_GGP
../lib/librte_net/rte_net.c:163:7: error: 'IPPROTO_IPIP' undeclared (first use in this function); did you mean 'IPPROTO_IPV4'?
case IPPROTO_IPIP:
^~~~~~~~~~~~
IPPROTO_IPV4
[83/229] Compiling C object lib/librte_mbuf.a.p/librte_mbuf_rte_mbuf_pool_ops.c.obj
[84/229] Compiling C object lib/librte_net.a.p/librte_net_rte_arp.c.obj
[85/229] Compiling C object lib/librte_net/libnet_crc_avx512_lib.a.p/net_crc_avx512.c.obj
[86/229] Compiling C object lib/librte_net.a.p/librte_net_rte_ether.c.obj
[87/229] Compiling C object lib/librte_mbuf.a.p/librte_mbuf_rte_mbuf_dyn.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 9.0 and gcc 8.1.0 (MinGW)

FreeBSD 11.2
	Kernel: 11.2
	Compiler: gcc 8.3

CentOS 8
	Kernel: 4.18.0.el8_0
	Compiler: gcc 8.3.1

openSUSE Leap 15
	Kernel: 4.12.14
	Compiler: gcc 7.4.1

Arch Linux
	Kernel: latest
	Compiler: gcc latest

Fedora 31
	Kernel: 5.3.16
	Compiler: gcc 9.2.1

Ubuntu 18.04 ARM
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

Ubuntu 18.04
	Kernel: 4.15.0-generic
	Compiler: gcc 7.5

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/15925/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

                 reply	other threads:[~2021-03-13 23:24 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=20210313232441.2F17C19DA1@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --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).