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| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio
Date: Thu, 28 Mar 2024 17:57:32 -0700 (PDT)	[thread overview]
Message-ID: <660611fc.050a0220.51e00.0448SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240328233338.56544-1-rdna@apple.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138965

_Testing PASS_

Submitter: Andrey Ignatov <rdna@apple.com>
Date: Thursday, March 28 2024 23:33:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:deedfb86a7a6e10064d3cccd593f62072de96e36

138965 --> testing pass

Test environment and result as below:

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


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 14.0.5

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

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

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

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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

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

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

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

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/29681/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-29  0:57 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240328233338.56544-1-rdna@apple.com>
2024-03-28 23:13 ` |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio Tx packed path qemudev
2024-03-28 23:17 ` qemudev
2024-03-29  0:17 ` |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio dpdklab
2024-03-29  0:18 ` dpdklab
2024-03-29  0:18 ` dpdklab
2024-03-29  0:18 ` dpdklab
2024-03-29  0:19 ` dpdklab
2024-03-29  0:19 ` dpdklab
2024-03-29  0:19 ` dpdklab
2024-03-29  0:19 ` dpdklab
2024-03-29  0:19 ` dpdklab
2024-03-29  0:19 ` dpdklab
2024-03-29  0:19 ` dpdklab
2024-03-29  0:20 ` dpdklab
2024-03-29  0:20 ` dpdklab
2024-03-29  0:23 ` dpdklab
2024-03-29  0:23 ` dpdklab
2024-03-29  0:24 ` dpdklab
2024-03-29  0:25 ` |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio Tx packed path 0-day Robot
2024-03-29  0:25 ` |SUCCESS| pw138965 [PATCH] vhost: optimize mbuf allocation in virtio dpdklab
2024-03-29  0:25 ` dpdklab
2024-03-29  0:25 ` dpdklab
2024-03-29  0:26 ` dpdklab
2024-03-29  0:27 ` dpdklab
2024-03-29  0:27 ` dpdklab
2024-03-29  0:27 ` dpdklab
2024-03-29  0:35 ` |FAILURE| " dpdklab
2024-03-29  0:35 ` |SUCCESS| " dpdklab
2024-03-29  0:35 ` dpdklab
2024-03-29  0:35 ` dpdklab
2024-03-29  0:36 ` dpdklab
2024-03-29  0:36 ` dpdklab
2024-03-29  0:36 ` dpdklab
2024-03-29  0:37 ` dpdklab
2024-03-29  0:44 ` dpdklab
2024-03-29  0:45 ` dpdklab
2024-03-29  0:45 ` dpdklab
2024-03-29  0:47 ` dpdklab
2024-03-29  0:48 ` dpdklab
2024-03-29  0:50 ` |FAILURE| " dpdklab
2024-03-29  0:50 ` |SUCCESS| " dpdklab
2024-03-29  0:51 ` dpdklab
2024-03-29  0:53 ` dpdklab
2024-03-29  0:54 ` dpdklab
2024-03-29  0:54 ` dpdklab
2024-03-29  0:55 ` dpdklab
2024-03-29  0:55 ` dpdklab
2024-03-29  0:56 ` dpdklab
2024-03-29  0:57 ` dpdklab [this message]
2024-03-29  0:57 ` dpdklab
2024-03-29  0:59 ` dpdklab
2024-03-29  1:03 ` dpdklab
2024-03-29  1:07 ` dpdklab
2024-03-29  1:10 ` dpdklab
2024-03-29  1:11 ` dpdklab
2024-03-29  1:12 ` |FAILURE| " dpdklab
2024-03-29  1:12 ` dpdklab
2024-03-29  1:13 ` |SUCCESS| " dpdklab
2024-03-29  1:13 ` dpdklab
2024-03-29  1:14 ` dpdklab
2024-03-29  1:17 ` dpdklab
2024-03-29  1:17 ` dpdklab
2024-03-29  1:19 ` dpdklab
2024-03-29  1:21 ` |FAILURE| " dpdklab
2024-03-29  1:24 ` dpdklab
2024-03-29  1:25 ` dpdklab
2024-03-29  1:29 ` dpdklab
2024-03-29  1:29 ` |SUCCESS| " dpdklab
2024-03-29  1:33 ` dpdklab
2024-03-29  1:39 ` |FAILURE| " dpdklab
2024-03-29  1:40 ` dpdklab
2024-03-29  1:42 ` dpdklab
2024-03-29  1:44 ` |SUCCESS| " dpdklab
2024-03-29  1:49 ` dpdklab
2024-03-29  1:51 ` |FAILURE| " dpdklab
2024-03-29  1:54 ` dpdklab
2024-03-29  1:55 ` dpdklab
2024-03-29  1:56 ` dpdklab
2024-03-29  2:00 ` |SUCCESS| " dpdklab
2024-03-29  2:05 ` dpdklab
2024-03-29  2:09 ` dpdklab
2024-03-29  2:12 ` dpdklab
2024-03-29  2:22 ` dpdklab
2024-03-29  3:06 ` dpdklab
2024-03-29  3:56 ` dpdklab
2024-04-02 18:25 ` dpdklab
2024-04-02 18:32 ` dpdklab
2024-04-02 18:37 ` dpdklab
2024-04-02 18:42 ` dpdklab
2024-04-02 19:02 ` 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=660611fc.050a0220.51e00.0448SMTPIN_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).