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] 680818068d31764357075cde440232ce5ab8b786
Date: Wed, 11 Sep 2024 10:26:01 -0700 (PDT) [thread overview]
Message-ID: <66e1d2a9.050a0220.1f83fd.1165SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing issues_
Branch: tags/v21.11
680818068d31764357075cde440232ce5ab8b786 --> functional testing issues
Upstream job id: Template-DTS-Pipeline#179863
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
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | FAIL |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30554/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-09-11 17:26 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 17:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-19 13:55 dpdklab
2024-09-19 12:42 dpdklab
2024-09-19 12:39 dpdklab
2024-09-19 11:58 dpdklab
2024-09-18 9:57 dpdklab
2024-09-18 8:41 dpdklab
2024-09-18 8:37 dpdklab
2024-09-18 5:08 dpdklab
2024-09-18 4:54 dpdklab
2024-09-18 4:52 dpdklab
2024-09-17 13:20 dpdklab
2024-09-17 9:54 dpdklab
2024-09-17 9:03 dpdklab
2024-09-17 8:52 dpdklab
2024-09-17 8:50 dpdklab
2024-09-17 6:21 dpdklab
2024-09-17 2:02 dpdklab
2024-09-17 0:20 dpdklab
2024-09-16 21:23 dpdklab
2024-09-16 9:37 dpdklab
2024-09-16 7:06 dpdklab
2024-09-16 4:37 dpdklab
2024-09-16 4:27 dpdklab
2024-09-15 23:54 dpdklab
2024-09-15 14:23 dpdklab
2024-09-15 7:40 dpdklab
2024-09-15 7:02 dpdklab
2024-09-15 6:09 dpdklab
2024-09-15 5:58 dpdklab
2024-09-15 4:36 dpdklab
2024-09-15 4:25 dpdklab
2024-09-14 8:28 dpdklab
2024-09-14 7:12 dpdklab
2024-09-13 10:15 dpdklab
2024-09-13 9:05 dpdklab
2024-09-13 7:12 dpdklab
2024-09-13 7:04 dpdklab
2024-09-12 12:44 dpdklab
2024-09-12 12:15 dpdklab
2024-09-12 12:14 dpdklab
2024-09-12 12:10 dpdklab
2024-09-12 12:10 dpdklab
2024-09-12 12:06 dpdklab
2024-09-12 12:03 dpdklab
2024-09-12 11:59 dpdklab
2024-09-12 11:51 dpdklab
2024-09-11 17:40 dpdklab
2024-09-11 17:36 dpdklab
2024-09-11 17:22 dpdklab
2024-09-11 13:05 dpdklab
2024-09-11 11:47 dpdklab
2024-09-10 17:24 dpdklab
2024-09-10 16:04 dpdklab
2024-09-10 16:01 dpdklab
2024-09-10 15:57 dpdklab
2024-09-10 12:23 dpdklab
2024-09-10 12:22 dpdklab
2024-09-10 11:33 dpdklab
2024-09-10 11:31 dpdklab
2024-09-10 11:30 dpdklab
2024-09-10 11:29 dpdklab
2024-09-09 8:36 dpdklab
2024-09-09 7:58 dpdklab
2024-09-09 7:54 dpdklab
2024-09-09 6:57 dpdklab
2024-09-09 6:45 dpdklab
2024-09-09 6:32 dpdklab
2024-09-09 6:28 dpdklab
2024-09-08 7:28 dpdklab
2024-09-08 7:28 dpdklab
2024-09-08 4:37 dpdklab
2024-09-08 4:31 dpdklab
2024-09-08 4:23 dpdklab
2024-09-08 4:19 dpdklab
2024-09-08 4:10 dpdklab
2024-09-07 15:56 dpdklab
2024-09-07 14:58 dpdklab
2024-09-07 14:50 dpdklab
2024-09-07 14:46 dpdklab
2024-09-07 11:48 dpdklab
2024-09-07 11:41 dpdklab
2024-09-07 11:37 dpdklab
2024-09-07 11:33 dpdklab
2024-09-06 16:23 dpdklab
2024-09-06 16:23 dpdklab
2024-09-06 15:33 dpdklab
2024-09-06 15:32 dpdklab
2024-09-06 15:19 dpdklab
2024-09-06 15:12 dpdklab
2024-09-06 15:12 dpdklab
2024-09-06 15:11 dpdklab
2024-09-06 15:11 dpdklab
2024-09-06 15:10 dpdklab
2024-09-06 15:06 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=66e1d2a9.050a0220.1f83fd.1165SMTPIN_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).