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| pw141157 [PATCH] [v10] examples/ptp: replace terms master
Date: Fri, 14 Jun 2024 15:14:28 -0700 (PDT)	[thread overview]
Message-ID: <666cc0c4.050a0220.fe268.bdabSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240614154615.65507-1-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, June 14 2024 15:41:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2e9586d502404c1cdc8da24118c681ff6ff1084a

141157 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+


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

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-14 22:14 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240614154615.65507-1-stephen@networkplumber.org>
2024-06-14 15:19 ` |SUCCESS| pw141157 [PATCH v10] examples/ptp: replace terms master and slave qemudev
2024-06-14 15:24 ` qemudev
2024-06-14 15:48 ` |WARNING| " checkpatch
2024-06-14 16:44 ` |SUCCESS| " 0-day Robot
2024-06-14 20:58 ` |SUCCESS| pw141157 [PATCH] [v10] examples/ptp: replace terms master dpdklab
2024-06-14 21:12 ` dpdklab
2024-06-14 21:13 ` dpdklab
2024-06-14 21:43 ` dpdklab
2024-06-14 21:48 ` dpdklab
2024-06-14 21:50 ` dpdklab
2024-06-14 21:50 ` dpdklab
2024-06-14 21:52 ` dpdklab
2024-06-14 21:52 ` dpdklab
2024-06-14 21:52 ` dpdklab
2024-06-14 21:57 ` dpdklab
2024-06-14 21:58 ` dpdklab
2024-06-14 21:59 ` dpdklab
2024-06-14 22:01 ` dpdklab
2024-06-14 22:01 ` dpdklab
2024-06-14 22:02 ` dpdklab
2024-06-14 22:03 ` dpdklab
2024-06-14 22:03 ` dpdklab
2024-06-14 22:03 ` dpdklab
2024-06-14 22:08 ` dpdklab
2024-06-14 22:08 ` dpdklab
2024-06-14 22:09 ` dpdklab
2024-06-14 22:10 ` dpdklab
2024-06-14 22:10 ` dpdklab
2024-06-14 22:11 ` dpdklab
2024-06-14 22:11 ` dpdklab
2024-06-14 22:11 ` dpdklab
2024-06-14 22:12 ` dpdklab
2024-06-14 22:12 ` dpdklab
2024-06-14 22:12 ` dpdklab
2024-06-14 22:12 ` dpdklab
2024-06-14 22:13 ` dpdklab
2024-06-14 22:13 ` dpdklab
2024-06-14 22:14 ` dpdklab
2024-06-14 22:14 ` dpdklab [this message]
2024-06-14 22:14 ` dpdklab
2024-06-14 22:15 ` dpdklab
2024-06-14 22:18 ` dpdklab
2024-06-14 22:19 ` dpdklab
2024-06-14 22:19 ` dpdklab
2024-06-14 22:20 ` dpdklab
2024-06-14 22:20 ` dpdklab
2024-06-14 22:21 ` dpdklab
2024-06-14 22:21 ` dpdklab
2024-06-14 22:21 ` dpdklab
2024-06-14 22:21 ` dpdklab
2024-06-14 22:22 ` dpdklab
2024-06-14 22:22 ` dpdklab
2024-06-14 22:22 ` dpdklab
2024-06-14 22:23 ` dpdklab
2024-06-14 22:23 ` dpdklab
2024-06-14 22:24 ` dpdklab
2024-06-14 22:25 ` dpdklab
2024-06-14 22:25 ` dpdklab
2024-06-14 22:26 ` dpdklab
2024-06-14 22:26 ` dpdklab
2024-06-14 22:32 ` dpdklab
2024-06-14 22:53 ` dpdklab
2024-06-14 22:54 ` dpdklab
2024-06-14 22:55 ` dpdklab
2024-06-14 22:55 ` dpdklab
2024-06-14 22:56 ` dpdklab
2024-06-14 22:56 ` dpdklab
2024-06-14 22:57 ` dpdklab
2024-06-14 22:57 ` dpdklab
2024-06-14 22:58 ` dpdklab
2024-06-14 22:58 ` dpdklab
2024-06-14 23:01 ` dpdklab
2024-06-14 23:03 ` dpdklab
2024-06-14 23:04 ` dpdklab
2024-06-14 23:04 ` dpdklab
2024-06-14 23:06 ` dpdklab
2024-06-14 23:07 ` dpdklab
2024-06-14 23:07 ` dpdklab
2024-06-14 23:08 ` dpdklab
2024-06-14 23:09 ` dpdklab
2024-06-14 23:10 ` dpdklab
2024-06-14 23:10 ` dpdklab
2024-06-14 23:10 ` dpdklab
2024-06-14 23:11 ` dpdklab
2024-06-14 23:19 ` dpdklab
2024-06-14 23:19 ` dpdklab
2024-06-14 23:20 ` dpdklab
2024-06-14 23:20 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:21 ` dpdklab
2024-06-14 23:22 ` dpdklab
2024-06-14 23:22 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:23 ` dpdklab
2024-06-14 23:24 ` dpdklab
2024-06-14 23:24 ` dpdklab
2024-06-14 23:25 ` dpdklab
2024-06-14 23:42 ` dpdklab
2024-06-14 23:42 ` dpdklab
2024-06-14 23:42 ` dpdklab
2024-06-14 23:49 ` dpdklab
2024-06-14 23:49 ` dpdklab
2024-06-14 23:50 ` dpdklab
2024-06-15  0:00 ` dpdklab
2024-06-15  0:03 ` dpdklab
2024-06-15  0:08 ` 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=666cc0c4.050a0220.fe268.bdabSMTPIN_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).