From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] e9b8b369deed1d368079e2591fa8df4a4b9dc94a
Date: Sat, 27 Apr 2024 01:17:34 -0700 (PDT) [thread overview]
Message-ID: <662cb49e.050a0220.76abe.9ec3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing issues_
Branch: tags/v21.11
e9b8b369deed1d368079e2591fa8df4a4b9dc94a --> functional testing fail
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/1
Failed Tests:
- scatter
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: x86_64-native-linuxapp-gcc
Fail/Total: 1/1
Failed Tests:
- scatter
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: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28958/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-04-27 8:17 UTC|newest]
Thread overview: 227+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 8:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-30 5:54 dpdklab
2024-04-30 5:26 dpdklab
2024-04-30 5:19 dpdklab
2024-04-30 5:17 dpdklab
2024-04-30 5:16 dpdklab
2024-04-30 5:16 dpdklab
2024-04-30 5:15 dpdklab
2024-04-30 5:15 dpdklab
2024-04-30 5:14 dpdklab
2024-04-30 5:14 dpdklab
2024-04-30 5:12 dpdklab
2024-04-30 5:11 dpdklab
2024-04-30 5:11 dpdklab
2024-04-30 5:07 dpdklab
2024-04-30 5:05 dpdklab
2024-04-30 5:04 dpdklab
2024-04-30 5:03 dpdklab
2024-04-30 5:02 dpdklab
2024-04-30 4:25 dpdklab
2024-04-30 4:23 dpdklab
2024-04-29 5:35 dpdklab
2024-04-29 5:33 dpdklab
2024-04-29 5:32 dpdklab
2024-04-29 5:31 dpdklab
2024-04-29 5:29 dpdklab
2024-04-29 5:28 dpdklab
2024-04-29 5:28 dpdklab
2024-04-29 5:27 dpdklab
2024-04-29 5:25 dpdklab
2024-04-29 5:22 dpdklab
2024-04-29 5:20 dpdklab
2024-04-29 5:19 dpdklab
2024-04-29 5:17 dpdklab
2024-04-29 5:13 dpdklab
2024-04-29 5:10 dpdklab
2024-04-29 5:06 dpdklab
2024-04-29 4:27 dpdklab
2024-04-29 4:25 dpdklab
2024-04-29 4:24 dpdklab
2024-04-29 4:22 dpdklab
2024-04-28 8:17 dpdklab
2024-04-28 6:45 dpdklab
2024-04-28 6:41 dpdklab
2024-04-28 6:34 dpdklab
2024-04-28 6:31 dpdklab
2024-04-28 5:39 dpdklab
2024-04-28 5:32 dpdklab
2024-04-28 5:30 dpdklab
2024-04-28 5:30 dpdklab
2024-04-28 5:28 dpdklab
2024-04-28 5:28 dpdklab
2024-04-28 5:27 dpdklab
2024-04-28 5:24 dpdklab
2024-04-28 5:20 dpdklab
2024-04-28 5:20 dpdklab
2024-04-28 5:20 dpdklab
2024-04-28 5:19 dpdklab
2024-04-28 5:17 dpdklab
2024-04-28 5:16 dpdklab
2024-04-27 7:45 dpdklab
2024-04-27 7:37 dpdklab
2024-04-27 7:15 dpdklab
2024-04-27 7:14 dpdklab
2024-04-27 7:11 dpdklab
2024-04-27 7:10 dpdklab
2024-04-27 7:09 dpdklab
2024-04-27 7:08 dpdklab
2024-04-27 7:05 dpdklab
2024-04-27 7:02 dpdklab
2024-04-27 7:01 dpdklab
2024-04-27 7:00 dpdklab
2024-04-27 7:00 dpdklab
2024-04-26 9:39 dpdklab
2024-04-26 7:41 dpdklab
2024-04-26 7:34 dpdklab
2024-04-26 7:30 dpdklab
2024-04-26 7:27 dpdklab
2024-04-26 6:51 dpdklab
2024-04-26 6:41 dpdklab
2024-04-26 6:36 dpdklab
2024-04-26 6:33 dpdklab
2024-04-26 6:29 dpdklab
2024-04-26 6:29 dpdklab
2024-04-26 6:23 dpdklab
2024-04-26 6:22 dpdklab
2024-04-26 6:20 dpdklab
2024-04-26 6:17 dpdklab
2024-04-26 6:11 dpdklab
2024-04-26 6:03 dpdklab
2024-04-26 5:52 dpdklab
2024-04-26 5:34 dpdklab
2024-04-25 7:29 dpdklab
2024-04-25 6:22 dpdklab
2024-04-25 6:15 dpdklab
2024-04-25 6:11 dpdklab
2024-04-25 6:08 dpdklab
2024-04-25 5:38 dpdklab
2024-04-25 5:33 dpdklab
2024-04-25 5:33 dpdklab
2024-04-25 5:32 dpdklab
2024-04-25 5:29 dpdklab
2024-04-25 5:29 dpdklab
2024-04-25 5:27 dpdklab
2024-04-25 5:24 dpdklab
2024-04-25 5:21 dpdklab
2024-04-25 5:19 dpdklab
2024-04-25 5:17 dpdklab
2024-04-25 5:16 dpdklab
2024-04-25 5:13 dpdklab
2024-04-24 7:31 dpdklab
2024-04-24 7:30 dpdklab
2024-04-24 7:19 dpdklab
2024-04-24 7:15 dpdklab
2024-04-24 7:08 dpdklab
2024-04-24 7:05 dpdklab
2024-04-24 6:26 dpdklab
2024-04-24 6:20 dpdklab
2024-04-24 6:18 dpdklab
2024-04-24 6:16 dpdklab
2024-04-24 6:15 dpdklab
2024-04-24 6:15 dpdklab
2024-04-24 6:11 dpdklab
2024-04-24 6:06 dpdklab
2024-04-24 6:05 dpdklab
2024-04-24 6:00 dpdklab
2024-04-24 5:53 dpdklab
2024-04-24 5:53 dpdklab
2024-04-23 8:18 dpdklab
2024-04-23 6:06 dpdklab
2024-04-23 6:00 dpdklab
2024-04-23 5:58 dpdklab
2024-04-23 5:56 dpdklab
2024-04-23 5:53 dpdklab
2024-04-23 5:52 dpdklab
2024-04-23 5:46 dpdklab
2024-04-23 5:39 dpdklab
2024-04-23 5:38 dpdklab
2024-04-23 5:33 dpdklab
2024-04-23 5:28 dpdklab
2024-04-23 5:26 dpdklab
2024-04-23 5:26 dpdklab
2024-04-23 5:25 dpdklab
2024-04-23 5:14 dpdklab
2024-04-23 5:09 dpdklab
2024-04-23 4:41 dpdklab
2024-04-23 4:36 dpdklab
2024-04-23 4:29 dpdklab
2024-04-23 4:28 dpdklab
2024-04-23 4:26 dpdklab
2024-04-22 8:33 dpdklab
2024-04-22 7:40 dpdklab
2024-04-22 7:38 dpdklab
2024-04-22 7:26 dpdklab
2024-04-22 7:00 dpdklab
2024-04-22 6:08 dpdklab
2024-04-22 6:00 dpdklab
2024-04-22 6:00 dpdklab
2024-04-22 5:59 dpdklab
2024-04-22 5:56 dpdklab
2024-04-22 5:56 dpdklab
2024-04-22 5:56 dpdklab
2024-04-22 5:53 dpdklab
2024-04-22 5:52 dpdklab
2024-04-22 5:48 dpdklab
2024-04-22 5:44 dpdklab
2024-04-22 5:44 dpdklab
2024-04-22 5:39 dpdklab
2024-04-21 8:17 dpdklab
2024-04-21 7:16 dpdklab
2024-04-21 7:08 dpdklab
2024-04-21 7:05 dpdklab
2024-04-21 7:02 dpdklab
2024-04-21 5:46 dpdklab
2024-04-21 5:42 dpdklab
2024-04-21 5:39 dpdklab
2024-04-21 5:36 dpdklab
2024-04-21 5:35 dpdklab
2024-04-21 5:34 dpdklab
2024-04-21 5:32 dpdklab
2024-04-21 5:30 dpdklab
2024-04-21 5:29 dpdklab
2024-04-21 5:29 dpdklab
2024-04-21 5:29 dpdklab
2024-04-21 5:29 dpdklab
2024-04-21 5:19 dpdklab
2024-04-21 5:19 dpdklab
2024-04-21 5:18 dpdklab
2024-04-20 8:16 dpdklab
2024-04-20 7:40 dpdklab
2024-04-20 7:37 dpdklab
2024-04-20 7:33 dpdklab
2024-04-20 7:25 dpdklab
2024-04-20 7:04 dpdklab
2024-04-20 6:07 dpdklab
2024-04-20 6:06 dpdklab
2024-04-20 6:03 dpdklab
2024-04-20 6:02 dpdklab
2024-04-20 6:00 dpdklab
2024-04-20 5:58 dpdklab
2024-04-20 5:55 dpdklab
2024-04-20 5:51 dpdklab
2024-04-20 5:45 dpdklab
2024-04-20 5:43 dpdklab
2024-04-20 5:28 dpdklab
2024-04-20 5:24 dpdklab
2024-04-20 5:23 dpdklab
2024-04-19 8:44 dpdklab
2024-04-19 8:01 dpdklab
2024-04-19 7:59 dpdklab
2024-04-19 7:59 dpdklab
2024-04-19 7:58 dpdklab
2024-04-19 7:57 dpdklab
2024-04-19 7:56 dpdklab
2024-04-19 7:55 dpdklab
2024-04-19 7:54 dpdklab
2024-04-19 7:53 dpdklab
2024-04-19 7:53 dpdklab
2024-04-19 7:50 dpdklab
2024-04-19 7:48 dpdklab
2024-04-19 7:47 dpdklab
2024-04-19 7:25 dpdklab
2024-04-19 7:19 dpdklab
2024-04-19 7:08 dpdklab
2024-04-19 7:07 dpdklab
2024-04-19 7:06 dpdklab
2024-04-19 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=662cb49e.050a0220.76abe.9ec3SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ktraynor@redhat.com \
--cc=test-report@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).