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] 4e50ad4469f7c037e32de5aa3535d1cd25de0741
Date: Thu, 18 Apr 2024 09:07:56 -0700 (PDT) [thread overview]
Message-ID: <6621455c.050a0220.204e4.3aa4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing issues_
Branch: 21.11-staging
4e50ad4469f7c037e32de5aa3535d1cd25de0741 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28870/
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-18 16:07 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 16:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-18 18:33 dpdklab
2024-04-18 16:11 dpdklab
2024-04-18 16:04 dpdklab
2024-04-18 15:57 dpdklab
2024-04-18 15:08 dpdklab
2024-04-18 14:57 dpdklab
2024-04-18 14:02 dpdklab
2024-04-18 14:01 dpdklab
2024-04-18 13:59 dpdklab
2024-04-18 13:59 dpdklab
2024-04-18 13:59 dpdklab
2024-04-18 13:57 dpdklab
2024-04-18 13:57 dpdklab
2024-04-18 13:56 dpdklab
2024-04-18 13:55 dpdklab
2024-04-18 13:54 dpdklab
2024-04-18 13:54 dpdklab
2024-04-18 13:53 dpdklab
2024-04-18 13:53 dpdklab
2024-04-18 13:52 dpdklab
2024-04-18 13:52 dpdklab
2024-04-18 13:51 dpdklab
2024-04-18 13:49 dpdklab
2024-04-18 13:48 dpdklab
2024-04-18 13:47 dpdklab
2024-04-18 13:46 dpdklab
2024-04-18 13:44 dpdklab
2024-04-18 13:43 dpdklab
2024-04-18 13:42 dpdklab
2024-04-18 13:39 dpdklab
2024-04-18 13:39 dpdklab
2024-04-18 13:38 dpdklab
2024-04-18 13:38 dpdklab
2024-04-18 13:26 dpdklab
2024-04-18 13:25 dpdklab
2024-04-18 13:24 dpdklab
2024-04-18 13:24 dpdklab
2024-04-18 13:23 dpdklab
2023-10-18 10:13 dpdklab
2023-10-17 5:14 dpdklab
2023-10-17 5:09 dpdklab
2023-10-16 22:45 dpdklab
2023-10-16 22:32 dpdklab
2023-09-02 5:32 dpdklab
2023-09-02 5:18 dpdklab
2023-09-02 5:09 dpdklab
2023-09-02 5:07 dpdklab
2023-09-02 4: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=6621455c.050a0220.204e4.3aa4SMTPIN_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).