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| pw142122 [PATCH] [v3] vfio: combine container_create and g
Date: Thu, 04 Jul 2024 05:55:24 -0700 (PDT)	[thread overview]
Message-ID: <66869bbc.050a0220.f020a.8401SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240703115943.44539-1-xiangwencheng@dayudpu.com>

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142122

_Testing PASS_

Submitter: BillXiang <xiangwencheng@dayudpu.com>
Date: Wednesday, July 03 2024 11:59:43 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:95bea772528d316c969a170e6206f3b05ac39413

142122 --> testing pass

Test environment and result as below:

+--------------------+----------------------+
|    Environment     | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS                 |
+--------------------+----------------------+


Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-04 12:55 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240703115943.44539-1-xiangwencheng@dayudpu.com>
2024-07-04  7:22 ` |SUCCESS| pw142122 [PATCH v3] vfio: combine container_create and group_bind qemudev
2024-07-04  7:26 ` qemudev
2024-07-04  7:48 ` |WARNING| " checkpatch
2024-07-04 12:27 ` |PENDING| pw142122 [PATCH] [v3] vfio: combine container_create and g dpdklab
2024-07-04 12:33 ` |SUCCESS| " dpdklab
2024-07-04 12:39 ` dpdklab
2024-07-04 12:41 ` dpdklab
2024-07-04 12:55 ` dpdklab [this message]
2024-07-04 13:36 ` dpdklab
2024-07-04 15:38 ` |PENDING| " dpdklab
2024-07-04 15:55 ` dpdklab
2024-07-04 15:57 ` dpdklab
2024-07-04 15:58 ` dpdklab
2024-07-04 16:01 ` dpdklab
2024-07-04 16:02 ` dpdklab
2024-07-04 16:05 ` dpdklab
2024-07-04 16:06 ` dpdklab
2024-07-04 16:07 ` dpdklab
2024-07-04 16:12 ` dpdklab
2024-07-04 16:16 ` dpdklab
2024-07-04 16:19 ` dpdklab
2024-07-04 16:19 ` dpdklab
2024-07-04 16:20 ` dpdklab
2024-07-04 19:33 ` |SUCCESS| " dpdklab
2024-07-04 21:33 ` |PENDING| " dpdklab
2024-07-04 21:41 ` |SUCCESS| " dpdklab
2024-07-04 22:16 ` dpdklab
2024-07-05  2:15 ` |PENDING| " dpdklab
2024-07-05  2:20 ` dpdklab
2024-07-05  2:56 ` dpdklab
2024-07-05  5:35 ` |SUCCESS| " dpdklab
2024-07-05  6:16 ` |PENDING| " dpdklab
2024-07-05  7:05 ` |SUCCESS| " dpdklab
2024-07-05  7:09 ` dpdklab
2024-07-05  7:14 ` dpdklab
2024-07-05  7:34 ` dpdklab
2024-07-05 10:59 ` |PENDING| " dpdklab
2024-07-05 10:59 ` dpdklab
2024-07-05 11:04 ` dpdklab
2024-07-05 11:07 ` dpdklab
2024-07-05 11:10 ` dpdklab
2024-07-05 11:11 ` dpdklab
2024-07-05 11:16 ` dpdklab
2024-07-05 11:17 ` dpdklab
2024-07-05 11:18 ` dpdklab
2024-07-05 11:21 ` dpdklab
2024-07-05 11:23 ` dpdklab
2024-07-05 11:24 ` dpdklab
2024-07-05 11:26 ` dpdklab
2024-07-05 11:27 ` dpdklab
2024-07-05 11:34 ` |SUCCESS| " dpdklab
2024-07-05 16:34 ` |PENDING| " dpdklab
2024-07-05 16:37 ` dpdklab
2024-07-05 16:38 ` dpdklab
2024-07-05 16:46 ` dpdklab
2024-07-05 16:53 ` dpdklab
2024-07-05 17:02 ` dpdklab
2024-07-05 17:10 ` dpdklab
2024-07-05 17:11 ` dpdklab
2024-07-05 17:19 ` dpdklab
2024-07-05 17:27 ` dpdklab
2024-07-05 17:40 ` dpdklab
2024-07-05 17:48 ` dpdklab
2024-07-05 17:51 ` dpdklab
2024-07-05 17:55 ` dpdklab
2024-07-05 17:56 ` dpdklab
2024-07-05 18:01 ` |SUCCESS| " dpdklab
2024-07-06 12:02 ` dpdklab
2024-07-06 13:31 ` dpdklab
2024-07-06 13:45 ` dpdklab
2024-07-08 15:25 ` dpdklab
2024-07-08 15:38 ` 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=66869bbc.050a0220.f020a.8401SMTPIN_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).