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| [GIT MASTER] b3485f4293997d35b6daecc3437bb0c183a51fb3
Date: Sat, 03 Aug 2024 17:30:30 -0700 (PDT)	[thread overview]
Message-ID: <66aecba6.5d0a0220.c3c3a.5767SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk

b3485f4293997d35b6daecc3437bb0c183a51fb3 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#172912

Test environment and result as below:

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


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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-08-04  0:30 UTC|newest]

Thread overview: 154+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04  0:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-09  3:01 dpdklab
2024-08-09  0:58 dpdklab
2024-08-09  0:58 dpdklab
2024-08-09  0:46 dpdklab
2024-08-09  0:24 dpdklab
2024-08-09  0:19 dpdklab
2024-08-09  0:18 dpdklab
2024-08-08 23:55 dpdklab
2024-08-08 23:48 dpdklab
2024-08-08 23:40 dpdklab
2024-08-08 23:10 dpdklab
2024-08-08 22:50 dpdklab
2024-08-08 22:45 dpdklab
2024-08-08 22:40 dpdklab
2024-08-08 22:33 dpdklab
2024-08-08 22:28 dpdklab
2024-08-08 21:56 dpdklab
2024-08-08 21:46 dpdklab
2024-08-08 21:43 dpdklab
2024-08-08 21:42 dpdklab
2024-08-08 21:41 dpdklab
2024-08-08 21:33 dpdklab
2024-08-08 21:21 dpdklab
2024-08-08 21:03 dpdklab
2024-08-08 20:59 dpdklab
2024-08-08 20:54 dpdklab
2024-08-08 20:35 dpdklab
2024-08-08 20:31 dpdklab
2024-08-08 20:31 dpdklab
2024-08-08 20:25 dpdklab
2024-08-08 20:25 dpdklab
2024-08-08 20:22 dpdklab
2024-08-08 20:10 dpdklab
2024-08-08 20:09 dpdklab
2024-08-08 20:02 dpdklab
2024-08-08 19:51 dpdklab
2024-08-08 19:42 dpdklab
2024-08-08 19:42 dpdklab
2024-08-08 19:41 dpdklab
2024-08-08 19:38 dpdklab
2024-08-08 19:37 dpdklab
2024-08-08 19:29 dpdklab
2024-08-08 19:24 dpdklab
2024-08-08 19:12 dpdklab
2024-08-08 19:05 dpdklab
2024-08-08 18:54 dpdklab
2024-08-08 18:43 dpdklab
2024-08-08  1:55 dpdklab
2024-08-08  1:23 dpdklab
2024-08-08  1:14 dpdklab
2024-08-08  1:10 dpdklab
2024-08-08  1:09 dpdklab
2024-08-08  1:06 dpdklab
2024-08-08  1:03 dpdklab
2024-08-08  0:59 dpdklab
2024-08-08  0:54 dpdklab
2024-08-08  0:50 dpdklab
2024-08-08  0:43 dpdklab
2024-08-08  0:40 dpdklab
2024-08-08  0:38 dpdklab
2024-08-08  0:30 dpdklab
2024-08-08  0:29 dpdklab
2024-08-08  0:28 dpdklab
2024-08-08  0:27 dpdklab
2024-08-08  0:25 dpdklab
2024-08-08  0:21 dpdklab
2024-08-08  0:20 dpdklab
2024-08-08  0:17 dpdklab
2024-08-06 23:35 dpdklab
2024-08-06 23:21 dpdklab
2024-08-06 23:13 dpdklab
2024-08-06 16:54 dpdklab
2024-08-06 16:40 dpdklab
2024-08-06 16:31 dpdklab
2024-08-06  7:50 dpdklab
2024-08-06  7:35 dpdklab
2024-08-06  7:26 dpdklab
2024-08-06  5:37 dpdklab
2024-08-06  5:23 dpdklab
2024-08-06  5:14 dpdklab
2024-08-06  2:03 dpdklab
2024-08-06  1:24 dpdklab
2024-08-06  1:18 dpdklab
2024-08-06  1:17 dpdklab
2024-08-06  1:06 dpdklab
2024-08-06  1:06 dpdklab
2024-08-06  0:58 dpdklab
2024-08-06  0:54 dpdklab
2024-08-06  0:53 dpdklab
2024-08-06  0:49 dpdklab
2024-08-06  0:48 dpdklab
2024-08-06  0:43 dpdklab
2024-08-06  0:42 dpdklab
2024-08-06  0:31 dpdklab
2024-08-06  0:30 dpdklab
2024-08-06  0:28 dpdklab
2024-08-06  0:25 dpdklab
2024-08-06  0:23 dpdklab
2024-08-04  1:57 dpdklab
2024-08-04  1:21 dpdklab
2024-08-04  1:15 dpdklab
2024-08-04  1:14 dpdklab
2024-08-04  1:13 dpdklab
2024-08-04  1:07 dpdklab
2024-08-04  1:04 dpdklab
2024-08-04  0:59 dpdklab
2024-08-04  0:49 dpdklab
2024-08-04  0:46 dpdklab
2024-08-04  0:43 dpdklab
2024-08-04  0:39 dpdklab
2024-08-04  0:27 dpdklab
2024-08-04  0:25 dpdklab
2024-08-04  0:22 dpdklab
2024-08-04  0:22 dpdklab
2024-08-04  0:15 dpdklab
2024-08-03  5:21 dpdklab
2024-08-03  3:02 dpdklab
2024-08-02  8:19 dpdklab
2024-08-02  7:29 dpdklab
2024-08-02  6:57 dpdklab
2024-08-02  6:56 dpdklab
2024-08-02  6:52 dpdklab
2024-08-02  5:26 dpdklab
2024-08-02  5:21 dpdklab
2024-08-02  4:51 dpdklab
2024-08-02  4:31 dpdklab
2024-08-02  4:27 dpdklab
2024-08-02  4:22 dpdklab
2024-08-02  3:59 dpdklab
2024-08-02  3:53 dpdklab
2024-08-02  3:49 dpdklab
2024-08-02  3:48 dpdklab
2024-08-02  3:47 dpdklab
2024-08-02  3:19 dpdklab
2024-08-02  3:18 dpdklab
2024-08-02  3:11 dpdklab
2024-08-02  3:05 dpdklab
2024-08-02  2:51 dpdklab
2024-08-02  2:51 dpdklab
2024-08-02  1:51 dpdklab
2024-08-02  1:31 dpdklab
2024-08-02  1:27 dpdklab
2024-08-02  1:22 dpdklab
2024-08-02  1:17 dpdklab
2024-08-02  0:39 dpdklab
2024-08-02  0:05 dpdklab
2024-08-01 23:57 dpdklab
2024-08-01 23:56 dpdklab
2024-08-01 23:37 dpdklab
2024-08-01 22:18 dpdklab
2024-08-01 21:49 dpdklab
2024-08-01 21:35 dpdklab
2024-08-01 21:02 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=66aecba6.5d0a0220.c3c3a.5767SMTPIN_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).