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| pw133030-133057 [PATCH] [v4,28/28] port: make API's stable
Date: Thu, 19 Oct 2023 20:45:56 -0700 (PDT)	[thread overview]
Message-ID: <6531f7f4.250a0220.a37d2.22bcSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, October 19 2023 19:10:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2cd2cf0cc53a508c4bd951a980ec534a646260de

133030-133057 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Debian Buster       | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+


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

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

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

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-20  3:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20  3:45 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-20  4:56 dpdklab
2023-10-20  4:29 dpdklab
2023-10-20  4:28 dpdklab
2023-10-20  4:27 dpdklab
2023-10-20  4:26 dpdklab
2023-10-20  4:06 dpdklab
2023-10-20  4:03 dpdklab
2023-10-20  4:00 dpdklab
2023-10-20  3:59 dpdklab
2023-10-20  3:56 dpdklab
2023-10-20  3:56 dpdklab
2023-10-20  3:55 dpdklab
2023-10-20  3:55 dpdklab
2023-10-20  3:51 dpdklab
2023-10-20  3:48 dpdklab
2023-10-20  3:47 dpdklab
2023-10-20  3:44 dpdklab
2023-10-20  3:43 dpdklab
2023-10-20  3:43 dpdklab
2023-10-20  3:43 dpdklab
2023-10-20  3:42 dpdklab
2023-10-20  3:42 dpdklab
2023-10-20  3:41 dpdklab
2023-10-20  3:41 dpdklab
2023-10-20  3:40 dpdklab
2023-10-20  3:39 dpdklab
2023-10-20  3:39 dpdklab
2023-10-20  3:38 dpdklab
2023-10-20  3:38 dpdklab
2023-10-20  3:36 dpdklab
2023-10-20  3:29 dpdklab
     [not found] <20231019191016.156430-29-stephen@networkplumber.org>
2023-10-19 18:57 ` |SUCCESS| pw133030-133057 [PATCH v4 28/28] " qemudev
2023-10-19 19:01 ` qemudev

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=6531f7f4.250a0220.a37d2.22bcSMTPIN_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).