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] 4b5abe7ec1ed2d43a285599bbba23f62ac049d8f
Date: Wed, 31 Jul 2024 03:25:15 -0700 (PDT)	[thread overview]
Message-ID: <66aa110b.050a0220.332d91.b63bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk-next-net

4b5abe7ec1ed2d43a285599bbba23f62ac049d8f --> functional testing pass

Upstream job id: Template-DTS-Pipeline#171906

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/tarballs/30069/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-31 11:24 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31 10:25 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-31 14:30 dpdklab
2024-07-31 11:20 dpdklab
2024-07-31 10:45 dpdklab
2024-07-31 10:20 dpdklab
2024-07-31 10:17 dpdklab
2024-07-31 10:16 dpdklab
2024-07-31 10:15 dpdklab
2024-07-31 10:11 dpdklab
2024-07-31  9:45 dpdklab
2024-07-31  9:33 dpdklab
2024-07-31  8:57 dpdklab
2024-07-31  8:08 dpdklab
2024-07-31  7:31 dpdklab
2024-07-31  7:29 dpdklab
2024-07-31  7:23 dpdklab
2024-07-31  7:23 dpdklab
2024-07-31  7:18 dpdklab
2024-07-31  7:08 dpdklab
2024-07-31  7:07 dpdklab
2024-07-31  7:05 dpdklab
2024-07-31  7:03 dpdklab
2024-07-31  6:59 dpdklab
2024-07-31  3:37 dpdklab
2024-07-31  0:49 dpdklab
2024-07-31  0:08 dpdklab
2024-07-30 23:49 dpdklab
2024-07-30 23:49 dpdklab
2024-07-30 23:49 dpdklab
2024-07-30 23:29 dpdklab
2024-07-30 23:24 dpdklab
2024-07-30 23:24 dpdklab
2024-07-30 23:23 dpdklab
2024-07-30 23:19 dpdklab
2024-07-30 23:14 dpdklab
2024-07-30 22:28 dpdklab
2024-07-30 21:54 dpdklab
2024-07-30 21:40 dpdklab
2024-07-30 21:33 dpdklab
2024-07-30 21:25 dpdklab
2024-07-30 21:21 dpdklab
2024-07-30 21:18 dpdklab
2024-07-30 21:17 dpdklab
2024-07-30 21:11 dpdklab
2024-07-30 21:08 dpdklab
2024-07-30 21:06 dpdklab
2024-07-30 21:03 dpdklab
2024-07-30  2:21 dpdklab
2024-07-30  1:53 dpdklab
2024-07-30  1:53 dpdklab
2024-07-30  1:21 dpdklab
2024-07-30  1:20 dpdklab
2024-07-30  1:15 dpdklab
2024-07-30  1:14 dpdklab
2024-07-30  1:13 dpdklab
2024-07-30  1:09 dpdklab
2024-07-30  1:04 dpdklab
2024-07-30  0:50 dpdklab
2024-07-30  0:46 dpdklab
2024-07-30  0:43 dpdklab
2024-07-30  0:42 dpdklab
2024-07-30  0:42 dpdklab
2024-07-30  0:39 dpdklab
2024-07-30  0:30 dpdklab
2024-07-30  0:29 dpdklab
2024-07-30  0:25 dpdklab
2024-07-30  0:23 dpdklab
2024-07-30  0:23 dpdklab
2024-07-30  0:22 dpdklab
2024-07-30  0:18 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=66aa110b.050a0220.332d91.b63bSMTPIN_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).