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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] b1a6f8deeee2d30b6e25d9a5c8279dfc9401d9aa
Date: Wed, 12 Jun 2024 20:50:45 -0700 (PDT)	[thread overview]
Message-ID: <666a6c95.050a0220.cb86e.1d21SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net

b1a6f8deeee2d30b6e25d9a5c8279dfc9401d9aa --> 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  |
+------------+--------+


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

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
Target: Unknown

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


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/29410/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-06-13  4:56 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  3:50 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-13  4:17 dpdklab
2024-06-13  4:16 dpdklab
2024-06-13  4:16 dpdklab
2024-06-13  4:06 dpdklab
2024-06-13  4:06 dpdklab
2024-06-13  4:01 dpdklab
2024-06-13  4:01 dpdklab
2024-06-13  4:01 dpdklab
2024-06-13  4:00 dpdklab
2024-06-13  4:00 dpdklab
2024-06-13  4:00 dpdklab
2024-06-13  4:00 dpdklab
2024-06-13  4:00 dpdklab
2024-06-13  4:00 dpdklab
2024-06-13  4:00 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:59 dpdklab
2024-06-13  3:58 dpdklab
2024-06-13  3:58 dpdklab
2024-06-13  3:58 dpdklab
2024-06-13  3:58 dpdklab
2024-06-13  3:58 dpdklab
2024-06-13  3:58 dpdklab
2024-06-13  3:58 dpdklab
2024-06-13  3:58 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:57 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:56 dpdklab
2024-06-13  3:55 dpdklab
2024-06-13  3:55 dpdklab
2024-06-13  3:55 dpdklab
2024-06-13  3:55 dpdklab
2024-06-13  3:54 dpdklab
2024-06-13  3:53 dpdklab
2024-06-13  3:53 dpdklab
2024-06-13  3:53 dpdklab
2024-06-13  3:53 dpdklab
2024-06-13  3:51 dpdklab
2024-06-13  3:50 dpdklab
2024-06-13  3:49 dpdklab
2024-06-13  3:49 dpdklab
2024-06-13  3:48 dpdklab
2024-06-13  3:48 dpdklab
2024-06-13  3:47 dpdklab
2024-06-13  3:47 dpdklab
2024-06-13  3:47 dpdklab
2024-06-13  3:47 dpdklab
2024-06-13  3:47 dpdklab
2024-06-13  3:47 dpdklab
2024-06-13  3:46 dpdklab
2024-06-13  3:46 dpdklab
2024-06-13  3:46 dpdklab
2024-06-13  3:44 dpdklab
2024-06-13  3:44 dpdklab
2024-06-13  3:44 dpdklab
2024-06-12  9:10 dpdklab
2024-06-12  8:18 dpdklab
2024-06-12  8:00 dpdklab
2024-06-12  7:02 dpdklab
2024-06-12  7:01 dpdklab
2024-06-12  7:01 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=666a6c95.050a0220.cb86e.1d21SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.com \
    --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).