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| pw142772-142773 [PATCH] [v2,2/2] doc: remove use of -n 4 o
Date: Wed, 31 Jul 2024 18:37:28 -0700 (PDT)	[thread overview]
Message-ID: <66aae6d8.050a0220.150183.d981SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240731043846.78174-2-stephen@networkplumber.org>

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, July 31 2024 04:38:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

142772-142773 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#172141

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

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


Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps

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


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-01  1:37 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240731043846.78174-2-stephen@networkplumber.org>
2024-07-31  4:23 ` |SUCCESS| pw142772-142773 [PATCH v2 2/2] doc: remove use of -n 4 option in documentation qemudev
2024-07-31  4:28 ` qemudev
2024-07-31  4:44 ` |WARNING| pw142773 " checkpatch
2024-07-31  6:02 ` |SUCCESS| " 0-day Robot
2024-07-31 19:30 ` |SUCCESS| pw142772-142773 [PATCH] [v2,2/2] doc: remove use of -n 4 o dpdklab
2024-07-31 19:30 ` |PENDING| " dpdklab
2024-07-31 19:33 ` |SUCCESS| " dpdklab
2024-07-31 19:41 ` dpdklab
2024-07-31 19:43 ` dpdklab
2024-07-31 19:52 ` dpdklab
2024-07-31 19:55 ` dpdklab
2024-07-31 19:57 ` dpdklab
2024-07-31 20:05 ` dpdklab
2024-07-31 20:58 ` |PENDING| " dpdklab
2024-07-31 21:05 ` |SUCCESS| " dpdklab
2024-07-31 21:12 ` |PENDING| " dpdklab
2024-07-31 21:17 ` dpdklab
2024-07-31 21:17 ` dpdklab
2024-07-31 21:24 ` |SUCCESS| " dpdklab
2024-07-31 21:25 ` dpdklab
2024-07-31 21:25 ` dpdklab
2024-07-31 21:39 ` |PENDING| " dpdklab
2024-07-31 21:40 ` |SUCCESS| " dpdklab
2024-07-31 21:56 ` |PENDING| " dpdklab
2024-07-31 22:08 ` dpdklab
2024-07-31 22:09 ` dpdklab
2024-07-31 22:11 ` dpdklab
2024-07-31 22:15 ` dpdklab
2024-07-31 22:16 ` dpdklab
2024-07-31 22:18 ` dpdklab
2024-07-31 22:23 ` |SUCCESS| " dpdklab
2024-07-31 22:24 ` |PENDING| " dpdklab
2024-07-31 22:25 ` dpdklab
2024-07-31 22:35 ` dpdklab
2024-07-31 22:40 ` dpdklab
2024-07-31 22:44 ` dpdklab
2024-07-31 22:46 ` dpdklab
2024-07-31 22:50 ` dpdklab
2024-07-31 22:52 ` dpdklab
2024-07-31 22:54 ` dpdklab
2024-07-31 22:55 ` dpdklab
2024-07-31 23:09 ` dpdklab
2024-07-31 23:11 ` dpdklab
2024-07-31 23:15 ` dpdklab
2024-07-31 23:18 ` dpdklab
2024-07-31 23:22 ` dpdklab
2024-07-31 23:26 ` dpdklab
2024-07-31 23:27 ` dpdklab
2024-07-31 23:27 ` dpdklab
2024-07-31 23:28 ` dpdklab
2024-07-31 23:32 ` dpdklab
2024-07-31 23:40 ` dpdklab
2024-07-31 23:41 ` dpdklab
2024-07-31 23:45 ` dpdklab
2024-08-01  0:37 ` dpdklab
2024-08-01  0:40 ` dpdklab
2024-08-01  0:41 ` dpdklab
2024-08-01  0:44 ` dpdklab
2024-08-01  0:46 ` dpdklab
2024-08-01  0:47 ` dpdklab
2024-08-01  0:52 ` dpdklab
2024-08-01  0:52 ` dpdklab
2024-08-01  0:53 ` dpdklab
2024-08-01  0:54 ` dpdklab
2024-08-01  0:58 ` |SUCCESS| " dpdklab
2024-08-01  0:58 ` dpdklab
2024-08-01  1:03 ` dpdklab
2024-08-01  1:05 ` dpdklab
2024-08-01  1:09 ` dpdklab
2024-08-01  1:14 ` dpdklab
2024-08-01  1:33 ` dpdklab
2024-08-01  1:37 ` dpdklab [this message]
2024-08-01  2:03 ` |PENDING| " dpdklab
2024-08-01  2:05 ` dpdklab
2024-08-01  2:07 ` dpdklab
2024-08-01  2:08 ` dpdklab
2024-08-01  2:09 ` dpdklab
2024-08-01  2:09 ` dpdklab
2024-08-01  2:09 ` dpdklab
2024-08-01  2:10 ` dpdklab
2024-08-01  2:10 ` dpdklab
2024-08-01  2:17 ` dpdklab
2024-08-01  2:22 ` dpdklab
2024-08-01  2:23 ` dpdklab
2024-08-01  2:25 ` dpdklab
2024-08-01  2:50 ` dpdklab
2024-08-01  2:51 ` dpdklab
2024-08-01  2:52 ` dpdklab
2024-08-01  2:58 ` dpdklab
2024-08-01  2:58 ` dpdklab
2024-08-01  3:01 ` dpdklab
2024-08-01  3:03 ` dpdklab
2024-08-01  3:05 ` dpdklab
2024-08-01  3:09 ` dpdklab
2024-08-01  3:10 ` dpdklab
2024-08-01  3:10 ` dpdklab
2024-08-01  3:11 ` dpdklab
2024-08-01  3:13 ` dpdklab
2024-08-01  3:13 ` dpdklab
2024-08-01  3:13 ` dpdklab
2024-08-01  3:14 ` dpdklab
2024-08-01  3:15 ` dpdklab
2024-08-01  3:18 ` dpdklab
2024-08-01  3:20 ` dpdklab
2024-08-01  3:23 ` dpdklab
2024-08-01  3:30 ` |SUCCESS| " dpdklab
2024-08-01  3:31 ` |PENDING| " dpdklab
2024-08-01  3:31 ` dpdklab
2024-08-01  3:44 ` |SUCCESS| " dpdklab
2024-08-02  7:40 ` 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=66aae6d8.050a0220.150183.d981SMTPIN_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).