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| pw132203 [PATCH] [v3] vhost: add IRQ suppression
Date: Fri, 29 Sep 2023 09:37:00 -0700 (PDT)	[thread overview]
Message-ID: <6516fd2c.170a0220.95da4.8293SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Friday, September 29 2023 10:38:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a89a9ca38ae61778a80f287677dc91e8bb3fbdfd

132203 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+


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

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-29 16:37 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 16:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-29 18:08 dpdklab
2023-09-29 18:05 dpdklab
2023-09-29 18:04 dpdklab
2023-09-29 18:04 dpdklab
2023-09-29 18:04 dpdklab
2023-09-29 18:03 dpdklab
2023-09-29 18:03 dpdklab
2023-09-29 18:01 dpdklab
2023-09-29 17:56 dpdklab
2023-09-29 17:52 dpdklab
2023-09-29 17:52 dpdklab
2023-09-29 17:50 dpdklab
2023-09-29 17:49 dpdklab
2023-09-29 17:49 dpdklab
2023-09-29 17:17 dpdklab
2023-09-29 17:16 dpdklab
2023-09-29 17:15 dpdklab
2023-09-29 17:14 dpdklab
2023-09-29 17:01 dpdklab
2023-09-29 16:57 dpdklab
2023-09-29 16:54 dpdklab
2023-09-29 16:49 dpdklab
2023-09-29 16:46 dpdklab
2023-09-29 16:41 dpdklab
2023-09-29 16:36 dpdklab
2023-09-29 16:35 dpdklab
2023-09-29 16:34 dpdklab
2023-09-29 16:29 dpdklab
2023-09-29 16:26 dpdklab
2023-09-29 16:25 dpdklab
2023-09-29 16:22 dpdklab
2023-09-29 16:11 dpdklab
2023-09-29 16:08 dpdklab
2023-09-29 16:07 dpdklab
2023-09-29 16:05 dpdklab
2023-09-29 16:04 dpdklab
2023-09-29 16:03 dpdklab
2023-09-29 16:03 dpdklab
2023-09-29 16:02 dpdklab
2023-09-29 16:01 dpdklab
2023-09-29 15:53 dpdklab
2023-09-29 15:51 dpdklab
2023-09-29 15:49 dpdklab
2023-09-29 15:47 dpdklab
2023-09-29 15:46 dpdklab
2023-09-29 15:42 dpdklab
2023-09-29 15:29 dpdklab
2023-09-29 15:28 dpdklab
2023-09-29 15:17 dpdklab
     [not found] <20230929103809.765417-1-maxime.coquelin@redhat.com>
2023-09-29 10:18 ` |SUCCESS| pw132203 [PATCH v3] " qemudev
2023-09-29 10:22 ` qemudev
2023-09-29 11:39 ` 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=6516fd2c.170a0220.95da4.8293SMTPIN_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).