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] |WARNING| [GIT MASTER] c4ddb113c5a6928ee8bb903cb8fe5708654ba167
Date: Thu, 28 May 2020 18:13:22 -0400 (EDT)	[thread overview]
Message-ID: <20200528221322.5AC146D4C6@noxus.dpdklab.iol.unh.edu> (raw)

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

_Testing issues_

Branch: dpdk-next-net-brcm

c4ddb113c5a6928ee8bb903cb8fe5708654ba167 --> testing fail

Test environment and result as below:

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

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 9.0

Fedora 31
	Kernel: 5.3.16
	Compiler: gcc 9.2.1

openSUSE Leap 15
	Kernel: 4.12.14
	Compiler: gcc 7.4.1

CentOS 8
	Kernel: 4.18.0.el8_0
	Compiler: gcc 8.3.1

Ubuntu 18.04
	Kernel: 4.15.0-generic
	Compiler: gcc 7.4

Arch Linux
	Kernel: latest
	Compiler: gcc latest

FreeBSD 11.2
	Kernel: 11.2
	Compiler: gcc 8.3

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/9801/

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2020-05-28 22:13 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=20200528221322.5AC146D4C6@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).