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: |SUCCESS| [GIT MASTER] 5c3cc79f4baca247938b7f9a3627cefdb7d62396
Date: Thu, 07 Nov 2024 08:49:52 -0800 (PST) [thread overview]
Message-ID: <672cefb0.050a0220.2525cb.1f46SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: 21.11-staging
5c3cc79f4baca247938b7f9a3627cefdb7d62396 --> testing pass
Upstream job id: Generic-Unit-Test-DPDK#289143
Test environment and result as below:
+-----------------------------+--------------+----------------+
| Environment | lpm_autotest | dpdk_unit_test |
+=============================+==============+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED |
+-----------------------------+--------------+----------------+
| 32-bit Ubuntu 22.04.4 (ARM) | SKIPPED | PASS |
+-----------------------------+--------------+----------------+
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
32-bit Ubuntu 22.04.4 (ARM)
Kernel: 5.15.83+ aarch64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/31458/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-11-07 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 16:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-07 18:28 dpdklab
2024-11-07 17:15 dpdklab
2024-11-07 17:01 dpdklab
2024-11-07 16:48 dpdklab
2024-11-07 16:36 dpdklab
2024-11-07 16:33 dpdklab
2024-11-07 16:30 dpdklab
2024-11-07 16:26 dpdklab
2024-11-07 16:24 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=672cefb0.050a0220.2525cb.1f46SMTPIN_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).