From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Chenbo Xia <chenbox@nvidia.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: |SUCCESS| [GIT MASTER] 289ddcad152ebffa7359e414526707eb3f2c0a4a
Date: Thu, 18 Jan 2024 04:09:30 -0800 (PST) [thread overview]
Message-ID: <65a914fa.d40a0220.d7024.5820SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-virtio
289ddcad152ebffa7359e414526707eb3f2c0a4a --> functional testing pass
Test environment and result as below:
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
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-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 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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/27710/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-18 12:09 UTC|newest]
Thread overview: 173+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 12:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 13:27 dpdklab
2024-01-18 17:42 dpdklab
2024-01-18 17:12 dpdklab
2024-01-18 14:59 dpdklab
2024-01-18 13:25 dpdklab
2024-01-18 13:14 dpdklab
2024-01-18 12:59 dpdklab
2024-01-18 12:47 dpdklab
2024-01-18 12:47 dpdklab
2024-01-18 12:47 dpdklab
2024-01-18 12:39 dpdklab
2024-01-18 12:38 dpdklab
2024-01-18 12:38 dpdklab
2024-01-18 12:38 dpdklab
2024-01-18 12:38 dpdklab
2024-01-18 12:37 dpdklab
2024-01-18 12:37 dpdklab
2024-01-18 12:31 dpdklab
2024-01-18 12:31 dpdklab
2024-01-18 12:30 dpdklab
2024-01-18 12:23 dpdklab
2024-01-18 12:22 dpdklab
2024-01-18 12:22 dpdklab
2024-01-18 12:20 dpdklab
2024-01-18 12:20 dpdklab
2024-01-18 12:20 dpdklab
2024-01-18 12:19 dpdklab
2024-01-18 12:18 dpdklab
2024-01-18 12:18 dpdklab
2024-01-18 12:17 dpdklab
2024-01-18 12:17 dpdklab
2024-01-18 12:17 dpdklab
2024-01-18 12:16 dpdklab
2024-01-18 12:16 dpdklab
2024-01-18 12:15 dpdklab
2024-01-18 12:15 dpdklab
2024-01-18 12:13 dpdklab
2024-01-18 12:12 dpdklab
2024-01-18 12:10 dpdklab
2024-01-18 12:10 dpdklab
2024-01-18 12:09 dpdklab
2024-01-18 12:09 dpdklab
2024-01-18 12:08 dpdklab
2024-01-18 12:06 dpdklab
2024-01-18 12:06 dpdklab
2024-01-18 12:00 dpdklab
2024-01-18 11:59 dpdklab
2024-01-18 11:59 dpdklab
2024-01-18 11:47 dpdklab
2024-01-18 11:47 dpdklab
2024-01-18 11:47 dpdklab
2024-01-18 11:46 dpdklab
2024-01-18 11:45 dpdklab
2024-01-18 11:45 dpdklab
2024-01-18 11:39 dpdklab
2024-01-18 11:38 dpdklab
2024-01-18 11:37 dpdklab
2024-01-04 23:13 dpdklab
2024-01-04 23:04 dpdklab
2024-01-04 12:10 dpdklab
2024-01-04 3:30 dpdklab
2024-01-04 1:21 dpdklab
2024-01-04 1:17 dpdklab
2024-01-04 1:12 dpdklab
2024-01-04 1:10 dpdklab
2024-01-04 1:03 dpdklab
2024-01-04 0:57 dpdklab
2024-01-04 0:40 dpdklab
2024-01-04 0:39 dpdklab
2024-01-04 0:38 dpdklab
2024-01-04 0:38 dpdklab
2024-01-04 0:38 dpdklab
2024-01-04 0:38 dpdklab
2024-01-04 0:36 dpdklab
2024-01-04 0:31 dpdklab
2024-01-04 0:30 dpdklab
2024-01-04 0:30 dpdklab
2024-01-04 0:29 dpdklab
2024-01-04 0:28 dpdklab
2024-01-04 0:27 dpdklab
2024-01-04 0:25 dpdklab
2024-01-04 0:25 dpdklab
2024-01-04 0:21 dpdklab
2024-01-04 0:21 dpdklab
2024-01-04 0:21 dpdklab
2024-01-04 0:19 dpdklab
2024-01-04 0:19 dpdklab
2024-01-04 0:19 dpdklab
2024-01-04 0:16 dpdklab
2024-01-04 0:15 dpdklab
2024-01-04 0:15 dpdklab
2024-01-04 0:15 dpdklab
2024-01-04 0:15 dpdklab
2024-01-04 0:15 dpdklab
2024-01-04 0:15 dpdklab
2024-01-04 0:12 dpdklab
2024-01-04 0:10 dpdklab
2024-01-04 0:10 dpdklab
2024-01-04 0:08 dpdklab
2024-01-04 0:02 dpdklab
2024-01-04 0:00 dpdklab
2024-01-04 0:00 dpdklab
2024-01-03 23:59 dpdklab
2024-01-03 23:32 dpdklab
2024-01-03 23:23 dpdklab
2024-01-03 23:22 dpdklab
2024-01-03 23:03 dpdklab
2024-01-03 23:03 dpdklab
2024-01-03 23:01 dpdklab
2024-01-03 23:00 dpdklab
2024-01-03 23:00 dpdklab
2024-01-03 22:57 dpdklab
2024-01-03 22:55 dpdklab
2023-12-12 20:37 dpdklab
2023-12-12 20:12 dpdklab
2023-12-12 20:08 dpdklab
2023-12-12 19:02 dpdklab
2023-12-12 18:42 dpdklab
2023-12-12 18:07 dpdklab
2023-12-12 18:07 dpdklab
2023-12-12 18:05 dpdklab
2023-12-12 18:05 dpdklab
2023-12-12 18:05 dpdklab
2023-12-12 18:05 dpdklab
2023-12-12 18:05 dpdklab
2023-12-12 18:03 dpdklab
2023-12-12 18:03 dpdklab
2023-12-12 18:03 dpdklab
2023-12-12 18:03 dpdklab
2023-12-12 18:02 dpdklab
2023-12-12 18:01 dpdklab
2023-12-12 18:01 dpdklab
2023-12-12 18:01 dpdklab
2023-12-12 18:01 dpdklab
2023-12-12 17:57 dpdklab
2023-12-12 17:57 dpdklab
2023-12-12 17:57 dpdklab
2023-12-12 17:57 dpdklab
2023-12-12 17:57 dpdklab
2023-12-12 17:56 dpdklab
2023-12-12 17:56 dpdklab
2023-12-12 17:56 dpdklab
2023-12-12 17:56 dpdklab
2023-12-12 17:54 dpdklab
2023-12-12 17:54 dpdklab
2023-12-12 17:54 dpdklab
2023-12-12 17:54 dpdklab
2023-12-12 17:54 dpdklab
2023-12-12 17:53 dpdklab
2023-12-12 17:53 dpdklab
2023-12-12 17:53 dpdklab
2023-12-12 17:48 dpdklab
2023-12-12 17:48 dpdklab
2023-12-12 17:48 dpdklab
2023-12-12 17:48 dpdklab
2023-12-12 17:48 dpdklab
2023-12-12 17:48 dpdklab
2023-12-12 17:47 dpdklab
2023-12-12 17:47 dpdklab
2023-12-12 17:47 dpdklab
2023-12-12 17:43 dpdklab
2023-12-12 17:43 dpdklab
2023-12-12 17:43 dpdklab
2023-12-12 17:34 dpdklab
2023-12-12 17:33 dpdklab
2023-12-12 17:33 dpdklab
2023-12-12 17:32 dpdklab
2023-12-12 17:31 dpdklab
2023-12-12 17:31 dpdklab
2023-12-12 17:30 dpdklab
2023-12-12 17:30 dpdklab
2023-12-12 17:29 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=65a914fa.d40a0220.d7024.5820SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=chenbox@nvidia.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=maxime.coquelin@redhat.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).