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] 7ce7d3341d7e21c2a81f2fea8e451681d7306d77
Date: Mon, 24 Feb 2025 12:08:20 -0800 (PST) [thread overview]
Message-ID: <67bcd1b4.630a0220.29f3d7.03c2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing issues_
Branch: tags/v22.11
7ce7d3341d7e21c2a81f2fea8e451681d7306d77 --> functional testing issues
Upstream job id: Template-DTS-Pipeline#213242
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| cmdline | PASS |
+-----------------+--------+
| dynamic_queue | PASS |
+-----------------+--------+
| ipv4_reassembly | FAIL |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/32620/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2025-02-24 20:08 UTC|newest]
Thread overview: 138+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 20:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-19 7:32 dpdklab
2025-02-19 6:37 dpdklab
2025-02-18 8:37 dpdklab
2025-02-18 7:19 dpdklab
2025-02-16 9:09 dpdklab
2025-02-16 7:52 dpdklab
2025-02-15 7:53 dpdklab
2025-02-15 7:40 dpdklab
2025-02-15 6:35 dpdklab
2025-02-14 9:36 dpdklab
2025-02-14 9:19 dpdklab
2025-02-14 8:03 dpdklab
2025-02-13 7:31 dpdklab
2025-02-13 7:31 dpdklab
2025-02-13 5:39 dpdklab
2025-02-12 7:02 dpdklab
2025-02-12 5:43 dpdklab
2025-02-11 10:10 dpdklab
2025-02-11 7:26 dpdklab
2025-02-10 9:11 dpdklab
2025-02-10 7:49 dpdklab
2025-02-09 7:07 dpdklab
2025-02-09 5:46 dpdklab
2025-02-08 14:25 dpdklab
2025-02-08 8:35 dpdklab
2025-02-07 12:46 dpdklab
2025-02-07 8:27 dpdklab
2025-02-06 16:02 dpdklab
2025-02-06 7:27 dpdklab
2025-02-05 7:20 dpdklab
2025-02-05 5:43 dpdklab
2025-02-04 8:20 dpdklab
2025-02-04 6:45 dpdklab
2025-02-03 8:29 dpdklab
2025-02-03 7:05 dpdklab
2025-02-02 8:27 dpdklab
2025-02-02 7:11 dpdklab
2025-02-01 7:34 dpdklab
2025-02-01 6:17 dpdklab
2025-01-31 9:18 dpdklab
2025-01-31 6:34 dpdklab
2025-01-30 9:19 dpdklab
2025-01-30 9:18 dpdklab
2025-01-30 6:44 dpdklab
2025-01-29 8:18 dpdklab
2025-01-29 6:25 dpdklab
2025-01-28 7:38 dpdklab
2025-01-28 5:50 dpdklab
2025-01-27 6:45 dpdklab
2025-01-27 5:33 dpdklab
2025-01-26 8:20 dpdklab
2025-01-26 6:45 dpdklab
2025-01-25 12:15 dpdklab
2025-01-25 12:14 dpdklab
2025-01-25 7:00 dpdklab
2025-01-24 7:50 dpdklab
2025-01-24 6:33 dpdklab
2025-01-23 8:45 dpdklab
2025-01-23 6:37 dpdklab
2025-01-22 7:32 dpdklab
2025-01-22 6:25 dpdklab
2025-01-20 8:39 dpdklab
2025-01-20 7:31 dpdklab
2025-01-19 7:26 dpdklab
2025-01-19 6:16 dpdklab
2025-01-18 8:42 dpdklab
2025-01-18 7:36 dpdklab
2025-01-17 8:07 dpdklab
2025-01-17 7:04 dpdklab
2025-01-16 7:46 dpdklab
2025-01-16 6:43 dpdklab
2025-01-15 9:20 dpdklab
2025-01-15 9:19 dpdklab
2025-01-15 7:32 dpdklab
2025-01-14 8:49 dpdklab
2025-01-14 7:15 dpdklab
2025-01-13 6:58 dpdklab
2025-01-13 6:13 dpdklab
2025-01-12 7:01 dpdklab
2025-01-12 5:43 dpdklab
2025-01-11 7:55 dpdklab
2025-01-11 6:24 dpdklab
2025-01-10 7:05 dpdklab
2025-01-10 6:03 dpdklab
2025-01-09 12:57 dpdklab
2025-01-09 2:48 dpdklab
2025-01-08 2:34 dpdklab
2025-01-08 2:34 dpdklab
2025-01-08 2:33 dpdklab
2025-01-08 2:33 dpdklab
2025-01-08 2:28 dpdklab
2025-01-08 2:26 dpdklab
2025-01-08 2:23 dpdklab
2025-01-08 2:21 dpdklab
2025-01-08 2:21 dpdklab
2025-01-08 2:17 dpdklab
2025-01-08 2:17 dpdklab
2025-01-06 7:54 dpdklab
2025-01-06 6:58 dpdklab
2025-01-05 7:44 dpdklab
2025-01-05 6:51 dpdklab
2025-01-04 7:15 dpdklab
2025-01-04 6:32 dpdklab
2025-01-03 8:53 dpdklab
2024-12-31 7:20 dpdklab
2024-12-31 6:34 dpdklab
2024-12-30 7:45 dpdklab
2024-12-30 7:00 dpdklab
2024-12-30 6:26 dpdklab
2024-12-29 7:42 dpdklab
2024-12-29 7:17 dpdklab
2024-12-29 7:17 dpdklab
2024-12-29 6:37 dpdklab
2024-12-28 7:55 dpdklab
2024-12-27 8:08 dpdklab
2024-12-27 7:20 dpdklab
2024-12-26 7:32 dpdklab
2024-12-26 6:46 dpdklab
2024-12-25 7:31 dpdklab
2024-12-24 9:12 dpdklab
2024-12-24 8:04 dpdklab
2024-12-23 7:37 dpdklab
2024-12-23 6:49 dpdklab
2024-12-22 7:32 dpdklab
2024-12-22 7:31 dpdklab
2024-12-21 8:26 dpdklab
2024-12-21 7:58 dpdklab
2024-12-21 7:57 dpdklab
2024-12-21 7:09 dpdklab
2024-12-20 8:54 dpdklab
2024-12-20 8:49 dpdklab
2024-12-20 7:53 dpdklab
2024-12-19 6:54 dpdklab
2024-12-19 6:46 dpdklab
2024-12-19 6:05 dpdklab
2024-12-18 10:52 dpdklab
2024-12-18 1:41 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=67bcd1b4.630a0220.29f3d7.03c2SMTPIN_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).