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| pw138658 [PATCH] vhost: cleanup vq resubmit info when set_
Date: Thu, 21 Mar 2024 15:25:56 -0700 (PDT)	[thread overview]
Message-ID: <65fcb3f4.050a0220.c0fc5.206cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240321095805.923117-1-haoqian.he@smartx.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138658

_Testing PASS_

Submitter: Haoqian He <haoqian.he@smartx.com>
Date: Thursday, March 21 2024 09:57:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:deedfb86a7a6e10064d3cccd593f62072de96e36

138658 --> testing pass

Test environment and result as below:

+--------------------------+----------------+
|       Environment        | dpdk_unit_test |
+==========================+================+
| Debian 12 (arm)          | PASS           |
+--------------------------+----------------+
| CentOS Stream 9 (ARM)    | PASS           |
+--------------------------+----------------+
| Debian 11 (Buster) (ARM) | PASS           |
+--------------------------+----------------+
| Fedora 37 (ARM)          | PASS           |
+--------------------------+----------------+


Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

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

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-21 22:26 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240321095805.923117-1-haoqian.he@smartx.com>
2024-03-21  9:44 ` |SUCCESS| pw138658 [PATCH] vhost: cleanup vq resubmit info when set_inflight_fd qemudev
2024-03-21  9:49 ` qemudev
2024-03-21 10:08 ` checkpatch
2024-03-21 11:04 ` 0-day Robot
2024-03-21 20:58 ` |SUCCESS| pw138658 [PATCH] vhost: cleanup vq resubmit info when set_ dpdklab
2024-03-21 21:02 ` dpdklab
2024-03-21 21:18 ` dpdklab
2024-03-21 21:20 ` dpdklab
2024-03-21 21:21 ` dpdklab
2024-03-21 21:24 ` dpdklab
2024-03-21 21:39 ` dpdklab
2024-03-21 21:45 ` dpdklab
2024-03-21 21:46 ` dpdklab
2024-03-21 21:48 ` dpdklab
2024-03-21 21:50 ` dpdklab
2024-03-21 22:01 ` dpdklab
2024-03-21 22:03 ` dpdklab
2024-03-21 22:05 ` dpdklab
2024-03-21 22:09 ` dpdklab
2024-03-21 22:11 ` dpdklab
2024-03-21 22:12 ` dpdklab
2024-03-21 22:18 ` dpdklab
2024-03-21 22:22 ` dpdklab
2024-03-21 22:23 ` dpdklab
2024-03-21 22:24 ` dpdklab
2024-03-21 22:25 ` dpdklab
2024-03-21 22:25 ` dpdklab
2024-03-21 22:25 ` dpdklab
2024-03-21 22:25 ` dpdklab [this message]
2024-03-21 22:26 ` dpdklab
2024-03-21 22:26 ` dpdklab
2024-03-21 22:26 ` dpdklab
2024-03-21 22:26 ` dpdklab
2024-03-21 22:27 ` dpdklab
2024-03-21 22:27 ` dpdklab
2024-03-21 22:27 ` dpdklab
2024-03-21 22:27 ` dpdklab
2024-03-21 22:27 ` dpdklab
2024-03-21 22:28 ` dpdklab
2024-03-21 22:28 ` dpdklab
2024-03-21 22:28 ` dpdklab
2024-03-21 22:28 ` dpdklab
2024-03-21 22:28 ` dpdklab
2024-03-21 22:29 ` dpdklab
2024-03-21 22:29 ` dpdklab
2024-03-21 22:29 ` dpdklab
2024-03-21 22:30 ` dpdklab
2024-03-21 22:30 ` dpdklab
2024-03-21 22:30 ` dpdklab
2024-03-21 22:30 ` dpdklab
2024-03-21 22:30 ` dpdklab
2024-03-21 22:30 ` dpdklab
2024-03-21 22:30 ` dpdklab
2024-03-21 22:30 ` dpdklab
2024-03-21 22:31 ` dpdklab
2024-03-21 22:31 ` dpdklab
2024-03-21 22:31 ` dpdklab
2024-03-21 22:31 ` dpdklab
2024-03-21 22:32 ` dpdklab
2024-03-21 22:32 ` dpdklab
2024-03-21 22:35 ` dpdklab
2024-03-21 22:35 ` dpdklab
2024-03-21 22:36 ` dpdklab
2024-03-21 22:38 ` dpdklab
2024-03-21 22:39 ` |FAILURE| " dpdklab
2024-03-21 22:42 ` |SUCCESS| " dpdklab
2024-03-21 22:43 ` |FAILURE| " dpdklab
2024-03-21 22:43 ` |SUCCESS| " dpdklab
2024-03-21 22:48 ` |FAILURE| " dpdklab
2024-03-21 22:50 ` dpdklab
2024-03-21 22:52 ` dpdklab
2024-03-21 23:01 ` |SUCCESS| " dpdklab
2024-03-21 23:07 ` dpdklab
2024-03-21 23:08 ` dpdklab
2024-03-21 23:13 ` dpdklab
2024-03-21 23:13 ` dpdklab
2024-03-21 23:23 ` |FAILURE| " dpdklab
2024-03-21 23:36 ` dpdklab
2024-03-22  1:10 ` |SUCCESS| " dpdklab
2024-03-22  1:33 ` dpdklab
2024-03-22  4:26 ` dpdklab
2024-03-23 16:10 ` dpdklab
2024-03-23 16:46 ` 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=65fcb3f4.050a0220.c0fc5.206cSMTPIN_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).