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] abaa473297cf21cb81e5348185a7694ae2f221e7
Date: Sun, 04 Jun 2023 18:37:53 -0700 (PDT)	[thread overview]
Message-ID: <647d3c71.4a0a0220.84448.b15cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk

abaa473297cf21cb81e5348185a7694ae2f221e7 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-05  1:37 UTC|newest]

Thread overview: 126+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  1:37 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-09 23:05 dpdklab
2023-06-09 22:31 dpdklab
2023-06-09 22:31 dpdklab
2023-06-09 22:30 dpdklab
2023-06-09 22:30 dpdklab
2023-06-09 22:30 dpdklab
2023-06-09 22:29 dpdklab
2023-06-09 22:20 dpdklab
2023-06-09 22:19 dpdklab
2023-06-09 22:19 dpdklab
2023-06-09 22:19 dpdklab
2023-06-09 22:19 dpdklab
2023-06-09 22:18 dpdklab
2023-06-09 22:14 dpdklab
2023-06-09 22:13 dpdklab
2023-06-09 22:13 dpdklab
2023-06-09 22:12 dpdklab
2023-06-09 22:12 dpdklab
2023-06-09 22:09 dpdklab
2023-06-09 22:07 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:06 dpdklab
2023-06-09 22:02 dpdklab
2023-06-09 22:02 dpdklab
2023-06-09 22:02 dpdklab
2023-06-09 22:01 dpdklab
2023-06-08 22:02 dpdklab
2023-06-08 22:02 dpdklab
2023-06-08 22:02 dpdklab
2023-06-08 22:01 dpdklab
2023-06-08 22:01 dpdklab
2023-06-08 22:01 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 22:00 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-08 21:59 dpdklab
2023-06-05  2:03 dpdklab
2023-06-05  1:57 dpdklab
2023-06-05  1:54 dpdklab
2023-06-05  1:33 dpdklab
2023-06-05  1:27 dpdklab
2023-06-05  1:23 dpdklab
2023-06-05  1:11 dpdklab
2023-06-05  1:10 dpdklab
2023-06-05  1:05 dpdklab
2023-06-05  1:04 dpdklab
2023-06-05  1:04 dpdklab
2023-06-05  1:03 dpdklab
2023-06-05  1:03 dpdklab
2023-06-04  1:59 dpdklab
2023-06-04  1:54 dpdklab
2023-06-04  1:44 dpdklab
2023-06-04  1:39 dpdklab
2023-06-04  1:35 dpdklab
2023-06-04  1:22 dpdklab
2023-06-04  1:10 dpdklab
2023-06-04  1:10 dpdklab
2023-06-04  1:03 dpdklab
2023-06-04  1:03 dpdklab
2023-06-04  1:02 dpdklab
2023-06-04  0:58 dpdklab
2023-06-04  0:57 dpdklab
2023-06-04  0:56 dpdklab
2023-06-03  2:50 dpdklab
2023-06-03  2:40 dpdklab
2023-06-03  2:35 dpdklab
2023-06-03  2:30 dpdklab
2023-06-03  2:14 dpdklab
2023-06-03  2:10 dpdklab
2023-06-03  1:23 dpdklab
2023-06-03  1:11 dpdklab
2023-06-03  1:10 dpdklab
2023-06-03  1:05 dpdklab
2023-06-03  1:05 dpdklab
2023-06-03  1:05 dpdklab
2023-06-03  1:04 dpdklab
2023-06-03  1:03 dpdklab
2023-06-02 20:54 dpdklab
2023-06-02 20:42 dpdklab
2023-06-02 20:25 dpdklab
2023-06-02 20:18 dpdklab
2023-06-02 20:09 dpdklab
2023-06-02 20:00 dpdklab
2023-06-02 19:48 dpdklab
2023-06-02 19:48 dpdklab
2023-06-02 19:44 dpdklab
2023-06-02 19:41 dpdklab
2023-06-02 19:41 dpdklab
2023-06-02 19:39 dpdklab
2023-06-02 19:35 dpdklab
2023-06-02 19:34 dpdklab
2023-06-02  2:07 dpdklab
2023-06-02  2:06 dpdklab
2023-06-02  1:47 dpdklab
2023-06-02  1:40 dpdklab
2023-06-02  1:23 dpdklab
2023-06-02  1:23 dpdklab
2023-06-02  1:11 dpdklab
2023-06-02  1:10 dpdklab
2023-06-02  1:04 dpdklab
2023-06-02  1:03 dpdklab
2023-06-02  1:02 dpdklab
2023-06-02  0:58 dpdklab
2023-06-02  0:58 dpdklab
2023-06-02  0:57 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=647d3c71.4a0a0220.84448.b15cSMTPIN_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).