automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125229 [PATCH] [v2] bus/auxiliary: support cleanup callback
Date: Fri, 24 Mar 2023 00:17:24 +0000 (UTC)	[thread overview]
Message-ID: <20230324001724.8E51260125@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125229

_Testing PASS_

Submitter: Xueming Li <xuemingl@nvidia.com>
Date: Friday, March 17 2023 15:24:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:bb1f2f5b181b9d8ea7fb28ca2024914fc57bd823

125229 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+


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

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-24  0:17 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24  0:17 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-24  0:16 dpdklab
2023-03-21 23:05 dpdklab
2023-03-21 21:09 dpdklab
2023-03-21  9:22 dpdklab
2023-03-20 19:24 dpdklab
2023-03-20 15:09 dpdklab
2023-03-20  0:50 dpdklab
2023-03-19 21:59 dpdklab
2023-03-19 12:56 dpdklab
2023-03-19 11:20 dpdklab
2023-03-17 18:47 dpdklab
2023-03-17 18:39 dpdklab
2023-03-17 18:10 dpdklab
2023-03-17 17:57 dpdklab
2023-03-17 17:51 dpdklab
2023-03-17 17:48 dpdklab
2023-03-17 17:45 dpdklab
2023-03-17 17:43 dpdklab
2023-03-17 17:38 dpdklab
2023-03-17 17:35 dpdklab
2023-03-17 17:25 dpdklab
2023-03-17 17:23 dpdklab
2023-03-17 17:20 dpdklab
2023-03-17 17:10 dpdklab
2023-03-17 17:05 dpdklab
2023-03-17 17:03 dpdklab
2023-03-17 16:58 dpdklab
2023-03-17 16:58 dpdklab
2023-03-17 16:51 dpdklab
2023-03-17 16:51 dpdklab
2023-03-17 16:37 dpdklab
2023-03-17 16:36 dpdklab
2023-03-17 16:31 dpdklab
2023-03-17 16:26 dpdklab
2023-03-17 16:23 dpdklab
2023-03-17 16:15 dpdklab
2023-03-17 16:12 dpdklab
2023-03-17 16:09 dpdklab
2023-03-17 16:06 dpdklab
2023-03-17 16:00 dpdklab
     [not found] <20230317152447.4570-1-xuemingl@nvidia.com>
2023-03-17 15:14 ` |SUCCESS| pw125229 [PATCH v2] " qemudev
2023-03-17 15:18 ` qemudev
2023-03-17 15:26 ` checkpatch
2023-03-17 17:59 ` 0-day Robot

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=20230324001724.8E51260125@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).