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, Tom Jones <thj@freebsd.org>
Subject: |FAILURE| pw139828 [PATCH] freebsd: Add support for multiple dpdk in
Date: Fri, 03 May 2024 07:00:51 -0700 (PDT)	[thread overview]
Message-ID: <6634ee13.0d0a0220.71aaa.e88aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240503094615.1427-1-thj@freebsd.org>

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/139828

_Testing issues_

Submitter: Tom Jones <thj@freebsd.org>
Date: Friday, May 03 2024 09:46:15 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139828 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| FreeBSD 13.3        | FAIL               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.0        | FAIL               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 38           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Debian 12           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 37           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 9     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 8     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Debian Bullseye     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| RHEL8               | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+

==== 20 line log output for FreeBSD 14.0 (dpdk_meson_compile): ====

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.0
	Kernel: 14.0
	Compiler: clang 16.0.6

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-03 14:00 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240503094615.1427-1-thj@freebsd.org>
2024-05-03 12:22 ` |SUCCESS| pw139828 [PATCH] freebsd: Add support for multiple dpdk instances on FreeBSD qemudev
2024-05-03 12:27 ` qemudev
2024-05-03 12:50 ` checkpatch
2024-05-03 13:39 ` |SUCCESS| pw139828 [PATCH] freebsd: Add support for multiple dpdk in dpdklab
2024-05-03 13:40 ` |FAILURE| " dpdklab
2024-05-03 13:41 ` |SUCCESS| " dpdklab
2024-05-03 13:41 ` dpdklab
2024-05-03 13:42 ` dpdklab
2024-05-03 13:42 ` dpdklab
2024-05-03 13:42 ` dpdklab
2024-05-03 13:43 ` dpdklab
2024-05-03 13:43 ` |FAILURE| " dpdklab
2024-05-03 13:43 ` dpdklab
2024-05-03 13:43 ` |SUCCESS| pw139828 [PATCH] freebsd: Add support for multiple dpdk instances on FreeBSD 0-day Robot
2024-05-03 13:44 ` |SUCCESS| pw139828 [PATCH] freebsd: Add support for multiple dpdk in dpdklab
2024-05-03 13:44 ` dpdklab
2024-05-03 13:44 ` dpdklab
2024-05-03 13:45 ` dpdklab
2024-05-03 13:45 ` |FAILURE| " dpdklab
2024-05-03 13:45 ` dpdklab
2024-05-03 13:45 ` dpdklab
2024-05-03 13:46 ` dpdklab
2024-05-03 13:46 ` |SUCCESS| " dpdklab
2024-05-03 13:47 ` |FAILURE| " dpdklab
2024-05-03 13:47 ` |SUCCESS| " dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:47 ` dpdklab
2024-05-03 13:48 ` |FAILURE| " dpdklab
2024-05-03 13:48 ` |SUCCESS| " dpdklab
2024-05-03 13:49 ` dpdklab
2024-05-03 13:50 ` |FAILURE| " dpdklab
2024-05-03 13:50 ` |SUCCESS| " dpdklab
2024-05-03 13:50 ` |FAILURE| " dpdklab
2024-05-03 13:51 ` dpdklab
2024-05-03 13:51 ` |SUCCESS| " dpdklab
2024-05-03 13:51 ` dpdklab
2024-05-03 13:51 ` dpdklab
2024-05-03 13:52 ` dpdklab
2024-05-03 13:52 ` dpdklab
2024-05-03 13:52 ` |FAILURE| " dpdklab
2024-05-03 13:52 ` |SUCCESS| " dpdklab
2024-05-03 13:53 ` dpdklab
2024-05-03 13:53 ` dpdklab
2024-05-03 13:55 ` dpdklab
2024-05-03 13:56 ` dpdklab
2024-05-03 13:56 ` dpdklab
2024-05-03 13:58 ` dpdklab
2024-05-03 13:58 ` dpdklab
2024-05-03 13:58 ` dpdklab
2024-05-03 13:58 ` |FAILURE| " dpdklab
2024-05-03 13:59 ` |SUCCESS| " dpdklab
2024-05-03 13:59 ` dpdklab
2024-05-03 13:59 ` |FAILURE| " dpdklab
2024-05-03 14:00 ` dpdklab [this message]
2024-05-03 14:01 ` |SUCCESS| " dpdklab
2024-05-03 14:02 ` dpdklab
2024-05-03 14:03 ` dpdklab
2024-05-03 14:03 ` dpdklab
2024-05-03 14:04 ` |FAILURE| " dpdklab
2024-05-03 14:05 ` |SUCCESS| " dpdklab
2024-05-03 14:06 ` dpdklab
2024-05-03 14:08 ` dpdklab
2024-05-03 14:10 ` dpdklab
2024-05-03 14:13 ` dpdklab
2024-05-03 14:17 ` dpdklab
2024-05-03 14:17 ` dpdklab
2024-05-03 14:18 ` dpdklab
2024-05-03 14:19 ` |FAILURE| " dpdklab
2024-05-03 14:21 ` |SUCCESS| " dpdklab
2024-05-03 14:23 ` dpdklab
2024-05-03 14:23 ` dpdklab
2024-05-03 14:32 ` dpdklab
2024-05-03 15:01 ` dpdklab
2024-05-03 15:06 ` dpdklab
2024-05-03 15:09 ` dpdklab
2024-05-03 15:25 ` dpdklab
2024-05-03 16:01 ` dpdklab
2024-05-03 20:12 ` dpdklab
2024-05-05  6:57 ` dpdklab
2024-05-05  7:16 ` dpdklab
2024-05-05  7:20 ` dpdklab
2024-05-05  7:24 ` dpdklab
2024-05-05  7:28 ` dpdklab
2024-05-06 11:32 ` 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=6634ee13.0d0a0220.71aaa.e88aSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thj@freebsd.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).