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| pw135106-135130 [PATCH] [v2,25/25] mempool/dpaa, mempool/d
Date: Wed, 13 Dec 2023 02:57:03 -0800 (PST)	[thread overview]
Message-ID: <65798dff.050a0220.de41.aef6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, December 13 2023 04:16:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f2d5afbb2c05d7647da7ea914887c52115652651

135106-135130 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | 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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-13 10:57 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 10:57 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-15 23:28 dpdklab
2023-12-13 17:18 dpdklab
2023-12-13 17:15 dpdklab
2023-12-13 17:06 dpdklab
2023-12-13 17:05 dpdklab
2023-12-13 17:04 dpdklab
2023-12-13 17:01 dpdklab
2023-12-13 17:01 dpdklab
2023-12-13 16:58 dpdklab
2023-12-13 16:55 dpdklab
2023-12-13 16:55 dpdklab
2023-12-13 16:54 dpdklab
2023-12-13 16:54 dpdklab
2023-12-13 16:52 dpdklab
2023-12-13 16:51 dpdklab
2023-12-13 16:35 dpdklab
2023-12-13 16:34 dpdklab
2023-12-13 16:11 dpdklab
2023-12-13 16:06 dpdklab
2023-12-13 15:53 dpdklab
2023-12-13 15:52 dpdklab
2023-12-13 15:52 dpdklab
2023-12-13 15:49 dpdklab
2023-12-13 15:49 dpdklab
2023-12-13 15:49 dpdklab
2023-12-13 15:47 dpdklab
2023-12-13 15:43 dpdklab
2023-12-13 15:42 dpdklab
2023-12-13 15:42 dpdklab
2023-12-13 15:38 dpdklab
2023-12-13 15:34 dpdklab
2023-12-13 15:33 dpdklab
2023-12-13 15:32 dpdklab
2023-12-13 15:32 dpdklab
2023-12-13 15:32 dpdklab
2023-12-13 15:31 dpdklab
2023-12-13 15:31 dpdklab
2023-12-13 15:24 dpdklab
2023-12-13 15:23 dpdklab
2023-12-13 11:21 dpdklab
2023-12-13 11:17 dpdklab
2023-12-13 11:17 dpdklab
2023-12-13 11:17 dpdklab
2023-12-13 11:15 dpdklab
2023-12-13 11:14 dpdklab
2023-12-13 11:14 dpdklab
2023-12-13 11:12 dpdklab
2023-12-13 11:09 dpdklab
2023-12-13 11:08 dpdklab
2023-12-13 11:08 dpdklab
2023-12-13 11:07 dpdklab
2023-12-13 11:05 dpdklab
2023-12-13 11:01 dpdklab
2023-12-13 10:58 dpdklab
2023-12-13 10:58 dpdklab
2023-12-13 10:57 dpdklab
2023-12-13 10:55 dpdklab
2023-12-13 10:54 dpdklab
2023-12-13 10:54 dpdklab
2023-12-13 10:52 dpdklab
2023-12-13 10:50 dpdklab
2023-12-13  9:08 dpdklab
2023-12-13  9:01 dpdklab
2023-12-13  9:00 dpdklab
2023-12-13  8:53 dpdklab
2023-12-13  8:38 dpdklab
2023-12-13  8:37 dpdklab
2023-12-13  8:30 dpdklab
2023-12-13  8:24 dpdklab
2023-12-13  8:21 dpdklab
2023-12-13  8:17 dpdklab
2023-12-13  8:01 dpdklab
2023-12-13  7:59 dpdklab
2023-12-13  7:59 dpdklab
2023-12-13  7:56 dpdklab
2023-12-13  7:53 dpdklab
2023-12-13  7:53 dpdklab
2023-12-13  7:48 dpdklab
2023-12-13  7:48 dpdklab
2023-12-13  7:47 dpdklab
2023-12-13  7:46 dpdklab
2023-12-13  7:45 dpdklab
2023-12-13  7:45 dpdklab
2023-12-13  7:44 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=65798dff.050a0220.de41.aef6SMTPIN_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).