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: |SUCCESS| pw139177 [PATCH] maintainers: change e-mail for vmxnet3
Date: Sat, 06 Apr 2024 05:53:43 -0700 (PDT)	[thread overview]
Message-ID: <661145d7.050a0220.49c50.efe9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240405215619.1887731-1-jochen.behrens@broadcom.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139177

_Testing PASS_

Submitter: Jochen Behrens <jochen.behrens@broadcom.com>
Date: Friday, April 05 2024 21:56:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139177 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+


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

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

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

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

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

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-06 12:53 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240405215619.1887731-1-jochen.behrens@broadcom.com>
2024-04-05 21:33 ` qemudev
2024-04-05 21:38 ` qemudev
2024-04-05 21:57 ` checkpatch
2024-04-05 22:44 ` 0-day Robot
2024-04-06 11:37 ` dpdklab
2024-04-06 11:38 ` dpdklab
2024-04-06 11:40 ` dpdklab
2024-04-06 11:41 ` dpdklab
2024-04-06 11:41 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:44 ` dpdklab
2024-04-06 11:45 ` dpdklab
2024-04-06 11:58 ` dpdklab
2024-04-06 11:58 ` dpdklab
2024-04-06 12:05 ` dpdklab
2024-04-06 12:05 ` dpdklab
2024-04-06 12:05 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:09 ` dpdklab
2024-04-06 12:09 ` dpdklab
2024-04-06 12:11 ` dpdklab
2024-04-06 12:13 ` dpdklab
2024-04-06 12:13 ` dpdklab
2024-04-06 12:13 ` dpdklab
2024-04-06 12:14 ` dpdklab
2024-04-06 12:15 ` dpdklab
2024-04-06 12:16 ` dpdklab
2024-04-06 12:19 ` dpdklab
2024-04-06 12:19 ` dpdklab
2024-04-06 12:19 ` dpdklab
2024-04-06 12:19 ` dpdklab
2024-04-06 12:20 ` dpdklab
2024-04-06 12:21 ` dpdklab
2024-04-06 12:21 ` |FAILURE| " dpdklab
2024-04-06 12:33 ` dpdklab
2024-04-06 12:33 ` |SUCCESS| " dpdklab
2024-04-06 12:34 ` |FAILURE| " dpdklab
2024-04-06 12:34 ` dpdklab
2024-04-06 12:35 ` |SUCCESS| " dpdklab
2024-04-06 12:35 ` dpdklab
2024-04-06 12:35 ` dpdklab
2024-04-06 12:35 ` dpdklab
2024-04-06 12:36 ` dpdklab
2024-04-06 12:39 ` |FAILURE| " dpdklab
2024-04-06 12:42 ` dpdklab
2024-04-06 12:43 ` |SUCCESS| " dpdklab
2024-04-06 12:44 ` dpdklab
2024-04-06 12:48 ` |FAILURE| " dpdklab
2024-04-06 12:49 ` |SUCCESS| " dpdklab
2024-04-06 12:50 ` dpdklab
2024-04-06 12:52 ` dpdklab
2024-04-06 12:53 ` dpdklab
2024-04-06 12:53 ` dpdklab
2024-04-06 12:53 ` |FAILURE| " dpdklab
2024-04-06 12:53 ` |SUCCESS| " dpdklab
2024-04-06 12:53 ` dpdklab [this message]
2024-04-06 12:53 ` dpdklab
2024-04-06 12:54 ` dpdklab
2024-04-06 12:54 ` dpdklab
2024-04-06 12:59 ` dpdklab
2024-04-06 12:59 ` dpdklab
2024-04-06 12:59 ` dpdklab
2024-04-06 13:00 ` dpdklab
2024-04-06 13:01 ` dpdklab
2024-04-06 13:17 ` dpdklab
2024-04-06 13:18 ` dpdklab
2024-04-06 13:18 ` dpdklab
2024-04-06 13:18 ` dpdklab
2024-04-06 13:19 ` dpdklab
2024-04-06 13:19 ` dpdklab
2024-04-06 13:20 ` dpdklab
2024-04-06 13:20 ` dpdklab
2024-04-06 13:20 ` dpdklab
2024-04-06 13:21 ` dpdklab
2024-04-06 13:21 ` |FAILURE| " dpdklab
2024-04-06 13:23 ` |SUCCESS| " dpdklab
2024-04-06 13:24 ` dpdklab
2024-04-06 13:25 ` dpdklab
2024-04-06 13:26 ` |FAILURE| " dpdklab
2024-04-06 13:27 ` |SUCCESS| " dpdklab
2024-04-06 13:27 ` dpdklab
2024-04-06 13:38 ` dpdklab
2024-04-06 13:39 ` dpdklab
2024-04-06 13:46 ` dpdklab
2024-04-06 13:58 ` dpdklab
2024-04-06 14:07 ` dpdklab
2024-04-06 14:11 ` dpdklab
2024-04-06 14:52 ` 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=661145d7.050a0220.49c50.efe9SMTPIN_ADDED_MISSING@mx.google.com \
    --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).