automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |SUCCESS| pw130169-130171 [PATCH] [v1,3/3] dma/idxd: add API to crea
Date: Fri, 11 Aug 2023 11:47:38 -0700 (PDT)	[thread overview]
Message-ID: <64d6824a.250a0220.4d464.874dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Friday, August 11 2023 16:14:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:70b6941e4e22d67bc10495d1638234a7e974f582

130169-130171 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+


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

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

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-11 18:47 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 18:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-12 12:15 dpdklab
2023-08-12 11:58 dpdklab
2023-08-12 11:53 dpdklab
2023-08-12 11:48 dpdklab
2023-08-12 11:44 dpdklab
2023-08-12 10:57 dpdklab
2023-08-12  3:04 dpdklab
2023-08-12  1:53 dpdklab
2023-08-12  1:53 dpdklab
2023-08-12  1:46 dpdklab
2023-08-12  1:46 dpdklab
2023-08-12  1:46 dpdklab
2023-08-12  1:37 dpdklab
2023-08-12  1:12 dpdklab
2023-08-12  1:05 dpdklab
2023-08-12  1:05 dpdklab
2023-08-11 20:01 dpdklab
2023-08-11 19:17 dpdklab
2023-08-11 19:17 dpdklab
2023-08-11 19:16 dpdklab
2023-08-11 19:13 dpdklab
2023-08-11 19:06 dpdklab
2023-08-11 18:56 dpdklab
2023-08-11 18:51 dpdklab
2023-08-11 18:51 dpdklab
2023-08-11 18:46 dpdklab
2023-08-11 18:42 dpdklab
2023-08-11 18:22 dpdklab
2023-08-11 18:21 dpdklab
2023-08-11 18:21 dpdklab
2023-08-11 18:01 dpdklab
2023-08-11 17:59 dpdklab
2023-08-11 17:56 dpdklab
2023-08-11 17:52 dpdklab
2023-08-11 17:52 dpdklab
2023-08-11 17:51 dpdklab
2023-08-11 17:51 dpdklab
2023-08-11 17:50 dpdklab
2023-08-11 17:50 dpdklab
2023-08-11 17:50 dpdklab
2023-08-11 17:50 dpdklab
2023-08-11 17:49 dpdklab
2023-08-11 17:49 dpdklab
2023-08-11 17:48 dpdklab
2023-08-11 17:48 dpdklab
2023-08-11 17:46 dpdklab
2023-08-11 17:45 dpdklab
2023-08-11 17:45 dpdklab
2023-08-11 17:44 dpdklab
2023-08-11 17:44 dpdklab
2023-08-11 17:40 dpdklab
2023-08-11 17:39 dpdklab
2023-08-11 17:38 dpdklab
2023-08-11 17:34 dpdklab
2023-08-11 17:34 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=64d6824a.250a0220.4d464.874dSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=anatoly.burakov@intel.com \
    --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).