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| pw140409-140428 [PATCH] [v10,20/20] drivers: remove use of
Date: Fri, 31 May 2024 23:01:10 -0700 (PDT)	[thread overview]
Message-ID: <665ab926.d40a0220.8fa19.95a1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240529233811.663211-21-stephen@networkplumber.org>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/140428

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, May 29 2024 23:33:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

140409-140428 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: Unknown

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


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

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-01  6:01 UTC|newest]

Thread overview: 150+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240529233811.663211-21-stephen@networkplumber.org>
2024-05-29 23:15 ` |SUCCESS| pw140409-140428 [PATCH v10 20/20] drivers: remove use of term sanity check qemudev
2024-05-29 23:19 ` qemudev
2024-05-29 23:41 ` |SUCCESS| pw140428 " checkpatch
2024-05-30  0:43 ` |FAILURE| " 0-day Robot
2024-05-30  7:53 ` |SUCCESS| pw140409-140428 [PATCH] [v10,20/20] drivers: remove use of dpdklab
2024-05-30  7:54 ` dpdklab
2024-05-30  8:13 ` dpdklab
2024-05-30  8:25 ` dpdklab
2024-05-30  8:25 ` dpdklab
2024-05-30  8:26 ` dpdklab
2024-05-30  8:27 ` dpdklab
2024-05-30  8:27 ` dpdklab
2024-05-30  8:28 ` dpdklab
2024-05-30  8:28 ` dpdklab
2024-05-30  8:29 ` dpdklab
2024-05-30  8:30 ` dpdklab
2024-05-30  8:32 ` dpdklab
2024-05-30  8:32 ` dpdklab
2024-05-30  8:33 ` dpdklab
2024-05-30  8:34 ` dpdklab
2024-05-30  8:34 ` dpdklab
2024-05-30  8:34 ` dpdklab
2024-05-30  8:35 ` dpdklab
2024-05-30  8:35 ` dpdklab
2024-05-30  8:36 ` dpdklab
2024-05-30  8:36 ` dpdklab
2024-05-30  8:37 ` dpdklab
2024-05-30  8:38 ` dpdklab
2024-05-30  8:38 ` dpdklab
2024-05-30  8:41 ` dpdklab
2024-05-30  8:42 ` dpdklab
2024-05-30  8:43 ` dpdklab
2024-05-30  8:45 ` dpdklab
2024-05-30  8:47 ` dpdklab
2024-05-30  8:50 ` dpdklab
2024-05-30  8:50 ` dpdklab
2024-05-30  8:51 ` dpdklab
2024-05-30  8:53 ` dpdklab
2024-05-30  8:55 ` dpdklab
2024-05-30  8:59 ` dpdklab
2024-05-30  9:00 ` dpdklab
2024-05-30  9:00 ` dpdklab
2024-05-30  9:02 ` dpdklab
2024-05-30  9:04 ` dpdklab
2024-05-30  9:46 ` dpdklab
2024-05-30  9:48 ` dpdklab
2024-05-30  9:49 ` dpdklab
2024-05-30 10:00 ` dpdklab
2024-05-30 10:01 ` dpdklab
2024-05-30 10:20 ` dpdklab
2024-05-30 10:23 ` dpdklab
2024-05-30 11:36 ` dpdklab
2024-05-30 11:42 ` dpdklab
2024-05-30 11:58 ` dpdklab
2024-05-30 17:54 ` dpdklab
2024-05-30 17:54 ` dpdklab
2024-05-30 18:39 ` dpdklab
2024-05-30 18:39 ` dpdklab
2024-05-30 18:45 ` dpdklab
2024-06-01  5:24 ` dpdklab
2024-06-01  5:54 ` dpdklab
2024-06-01  5:55 ` dpdklab
2024-06-01  6:01 ` dpdklab [this message]
2024-06-01  6:01 ` dpdklab
2024-06-01  6:22 ` dpdklab
2024-06-01  6:27 ` dpdklab
2024-06-01  7:10 ` dpdklab
2024-06-01  7:27 ` dpdklab
2024-06-01  7:29 ` dpdklab
2024-06-01  7:30 ` dpdklab
2024-06-01  7:33 ` dpdklab
2024-06-01  7:35 ` dpdklab
2024-06-01  7:35 ` dpdklab
2024-06-01  7:36 ` dpdklab
2024-06-01  7:37 ` dpdklab
2024-06-01  7:37 ` dpdklab
2024-06-01  7:41 ` dpdklab
2024-06-01  8:03 ` dpdklab
2024-06-01  8:04 ` dpdklab
2024-06-01 10:40 ` dpdklab
2024-06-01 10:42 ` dpdklab
2024-06-01 10:58 ` dpdklab
2024-06-01 11:00 ` dpdklab
2024-06-01 11:03 ` dpdklab
2024-06-01 11:04 ` dpdklab
2024-06-01 11:05 ` dpdklab
2024-06-01 11:11 ` dpdklab
2024-06-01 11:12 ` dpdklab
2024-06-01 11:13 ` dpdklab
2024-06-01 11:14 ` dpdklab
2024-06-01 11:14 ` dpdklab
2024-06-01 11:16 ` dpdklab
2024-06-01 11:17 ` dpdklab
2024-06-01 11:18 ` dpdklab
2024-06-01 11:18 ` dpdklab
2024-06-01 11:19 ` dpdklab
2024-06-01 11:22 ` dpdklab
2024-06-01 11:25 ` dpdklab
2024-06-01 11:26 ` dpdklab
2024-06-01 11:28 ` dpdklab
2024-06-01 11:39 ` dpdklab
2024-06-01 11:40 ` dpdklab
2024-06-01 11:41 ` dpdklab
2024-06-01 11:45 ` dpdklab
2024-06-01 11:45 ` dpdklab
2024-06-01 11:45 ` dpdklab
2024-06-01 11:45 ` dpdklab
2024-06-01 11:49 ` dpdklab
2024-06-01 11:54 ` dpdklab
2024-06-01 11:55 ` dpdklab
2024-06-01 11:55 ` dpdklab
2024-06-01 11:56 ` dpdklab
2024-06-01 11:56 ` dpdklab
2024-06-01 11:56 ` dpdklab
2024-06-01 11:57 ` dpdklab
2024-06-01 11:58 ` dpdklab
2024-06-01 11:58 ` dpdklab
2024-06-01 11:58 ` dpdklab
2024-06-01 11:59 ` dpdklab
2024-06-01 12:10 ` dpdklab
2024-06-01 12:10 ` dpdklab
2024-06-01 12:12 ` dpdklab
2024-06-01 12:13 ` dpdklab
2024-06-01 12:13 ` dpdklab
2024-06-01 12:13 ` dpdklab
2024-06-01 12:13 ` dpdklab
2024-06-01 12:13 ` dpdklab
2024-06-01 12:14 ` dpdklab
2024-06-01 12:14 ` dpdklab
2024-06-01 12:15 ` dpdklab
2024-06-01 12:22 ` dpdklab
2024-06-01 12:23 ` dpdklab
2024-06-01 12:57 ` dpdklab
2024-06-01 13:24 ` dpdklab
2024-06-01 13:24 ` dpdklab
2024-06-01 13:34 ` dpdklab
2024-06-01 13:35 ` dpdklab
2024-06-01 13:40 ` dpdklab
2024-06-01 13:42 ` dpdklab
2024-06-01 13:44 ` dpdklab
2024-06-01 13:44 ` dpdklab
2024-06-01 13:51 ` dpdklab
2024-06-01 14:21 ` dpdklab
2024-06-01 14:23 ` dpdklab
2024-06-01 14:24 ` dpdklab
2024-06-01 14:51 ` dpdklab
2024-06-01 15:19 ` dpdklab
2024-06-01 19:16 ` dpdklab
2024-06-01 19:32 ` dpdklab
2024-06-01 23:38 ` 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=665ab926.d40a0220.8fa19.95a1SMTPIN_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).