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| [GIT MASTER] 643752207964b2abd0863d9b3dc7522a40469ba0
Date: Thu, 18 Mar 2021 14:34:13 -0400 (EDT)	[thread overview]
Message-ID: <20210318183413.7926630565@noxus.dpdklab.iol.unh.edu> (raw)

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

_Testing issues_

Branch: dpdk

643752207964b2abd0863d9b3dc7522a40469ba0 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Ubuntu 18.04 (dpdk_meson_compile): ====
An uncaught exception was raised. We may already know about the issue. If your patch is not run again after one business day, feel free to contact us to let us know.
Traceback (most recent call last):
File "/opt/dpdklab/dpdklab-ci/compile_meson_with_podman.py", line 52, in <module>
raise e
File "/opt/dpdklab/dpdklab-ci/compile_meson_with_podman.py", line 45, in <module>
compile_dpdk.build()
File "/opt/dpdklab/dpdklab-ci/compile_meson_with_podman.py", line 31, in build
self.image_build(image)
File "/opt/dpdklab/dpdklab-ci/ci.py", line 208, in image_build
cwd=script_dir + '/containers')
File "/opt/dpdklab/dpdklab-ci/ci.py", line 186, in check_call
subprocess.check_call(command, **kwargs)
File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '('podman', 'build', '-t', 'ubuntu18.04/dpdk_compile', '-f', 'ubuntu18.04/dpdk_compile.Dockerfile', '.')' returned non-zero exit status 125.
==== End log output ====

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

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

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)

CentOS 8
	Kernel: 4.18.0.el8_0
	Compiler: gcc 8.3.1

FreeBSD 11.2
	Kernel: 11.2
	Compiler: gcc 8.3

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: latest
	Compiler: gcc latest

openSUSE Leap 15
	Kernel: 4.12.14
	Compiler: gcc 7.4.1

Fedora 31
	Kernel: 5.3.16
	Compiler: gcc 9.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/tarballs/14166/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-03-18 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 18:34 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-18 18:12 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=20210318183413.7926630565@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).