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| pw140199-140206 [PATCH] [v8,8/8] net/null: use generic SW
Date: Tue, 21 May 2024 12:08:02 -0700 (PDT)	[thread overview]
Message-ID: <664cf112.170a0220.35b6.14eaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240521170453.119036-9-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, May 21 2024 17:00:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33

140199-140206 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+


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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-21 19:08 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240521170453.119036-9-stephen@networkplumber.org>
2024-05-21 17:01 ` |SUCCESS| pw140199-140206 [PATCH v8 8/8] net/null: use generic SW stats qemudev
2024-05-21 17:06 ` qemudev
2024-05-21 17:08 ` |SUCCESS| pw140206 " checkpatch
2024-05-21 18:07 ` |FAILURE| " 0-day Robot
2024-05-21 18:19 ` |SUCCESS| pw140199-140206 [PATCH] [v8,8/8] net/null: use generic SW dpdklab
2024-05-21 18:22 ` dpdklab
2024-05-21 18:22 ` dpdklab
2024-05-21 18:23 ` dpdklab
2024-05-21 18:26 ` dpdklab
2024-05-21 18:42 ` dpdklab
2024-05-21 18:42 ` dpdklab
2024-05-21 18:44 ` dpdklab
2024-05-21 18:45 ` dpdklab
2024-05-21 18:46 ` dpdklab
2024-05-21 18:57 ` dpdklab
2024-05-21 18:57 ` dpdklab
2024-05-21 18:58 ` dpdklab
2024-05-21 18:59 ` dpdklab
2024-05-21 18:59 ` dpdklab
2024-05-21 19:00 ` dpdklab
2024-05-21 19:00 ` dpdklab
2024-05-21 19:01 ` dpdklab
2024-05-21 19:04 ` dpdklab
2024-05-21 19:05 ` dpdklab
2024-05-21 19:08 ` dpdklab [this message]
2024-05-21 19:09 ` dpdklab
2024-05-21 19:09 ` dpdklab
2024-05-21 19:10 ` dpdklab
2024-05-21 19:10 ` dpdklab
2024-05-21 19:12 ` dpdklab
2024-05-21 19:12 ` dpdklab
2024-05-21 19:12 ` dpdklab
2024-05-21 19:13 ` dpdklab
2024-05-21 19:13 ` dpdklab
2024-05-21 19:13 ` dpdklab
2024-05-21 19:14 ` dpdklab
2024-05-21 19:14 ` dpdklab
2024-05-21 19:14 ` dpdklab
2024-05-21 19:14 ` dpdklab
2024-05-21 19:15 ` dpdklab
2024-05-21 19:16 ` dpdklab
2024-05-21 19:16 ` dpdklab
2024-05-21 19:17 ` dpdklab
2024-05-21 19:17 ` dpdklab
2024-05-21 19:17 ` dpdklab
2024-05-21 19:18 ` dpdklab
2024-05-21 19:18 ` dpdklab
2024-05-21 19:18 ` dpdklab
2024-05-21 19:19 ` dpdklab
2024-05-21 19:19 ` dpdklab
2024-05-21 19:19 ` dpdklab
2024-05-21 19:19 ` dpdklab
2024-05-21 19:20 ` dpdklab
2024-05-21 19:20 ` dpdklab
2024-05-21 19:21 ` dpdklab
2024-05-21 19:22 ` dpdklab
2024-05-21 19:22 ` dpdklab
2024-05-21 19:22 ` dpdklab
2024-05-21 19:23 ` dpdklab
2024-05-21 19:23 ` dpdklab
2024-05-21 19:23 ` dpdklab
2024-05-21 19:24 ` dpdklab
2024-05-21 19:24 ` dpdklab
2024-05-21 19:24 ` dpdklab
2024-05-21 19:24 ` dpdklab
2024-05-21 19:25 ` dpdklab
2024-05-21 19:27 ` dpdklab
2024-05-21 19:28 ` dpdklab
2024-05-21 19:28 ` dpdklab
2024-05-21 19:29 ` dpdklab
2024-05-21 19:29 ` dpdklab
2024-05-21 19:32 ` dpdklab
2024-05-21 19:32 ` dpdklab
2024-05-21 19:32 ` dpdklab
2024-05-21 19:33 ` dpdklab
2024-05-21 19:34 ` dpdklab
2024-05-21 19:35 ` dpdklab
2024-05-21 19:35 ` dpdklab
2024-05-21 19:37 ` dpdklab
2024-05-21 19:37 ` dpdklab
2024-05-21 19:38 ` dpdklab
2024-05-21 19:39 ` dpdklab
2024-05-21 19:39 ` dpdklab
2024-05-21 19:40 ` dpdklab
2024-05-21 19:43 ` dpdklab
2024-05-21 19:46 ` dpdklab
2024-05-21 19:47 ` |FAILURE| " dpdklab
2024-05-21 20:15 ` |SUCCESS| " dpdklab
2024-05-21 20:16 ` dpdklab
2024-05-21 20:17 ` dpdklab
2024-05-21 20:28 ` dpdklab
2024-05-21 22:01 ` dpdklab
2024-05-23  6:05 ` 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=664cf112.170a0220.35b6.14eaSMTPIN_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).