From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136230-136231 [PATCH] [v2,2/2] app/testpmd: add support
Date: Wed, 31 Jan 2024 02:49:44 -0800 (PST) [thread overview]
Message-ID: <65ba25c8.810a0220.d46ee.2a3aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136231
_Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Wednesday, January 31 2024 09:38:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca
136230-136231 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29000/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-31 10:49 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 10:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-31 11:34 dpdklab
2024-01-31 11:34 dpdklab
2024-01-31 11:32 dpdklab
2024-01-31 11:27 dpdklab
2024-01-31 11:14 dpdklab
2024-01-31 11:11 dpdklab
2024-01-31 11:06 dpdklab
2024-01-31 11:06 dpdklab
2024-01-31 11:05 dpdklab
2024-01-31 11:05 dpdklab
2024-01-31 11:04 dpdklab
2024-01-31 11:02 dpdklab
2024-01-31 11:02 dpdklab
2024-01-31 11:00 dpdklab
2024-01-31 10:59 dpdklab
2024-01-31 10:59 dpdklab
2024-01-31 10:58 dpdklab
2024-01-31 10:58 dpdklab
2024-01-31 10:58 dpdklab
2024-01-31 10:58 dpdklab
2024-01-31 10:57 dpdklab
2024-01-31 10:57 dpdklab
2024-01-31 10:56 dpdklab
2024-01-31 10:55 dpdklab
2024-01-31 10:54 dpdklab
2024-01-31 10:54 dpdklab
2024-01-31 10:54 dpdklab
2024-01-31 10:53 dpdklab
2024-01-31 10:53 dpdklab
2024-01-31 10:51 dpdklab
2024-01-31 10:47 dpdklab
2024-01-31 10:47 dpdklab
2024-01-31 10:46 dpdklab
2024-01-31 10:38 dpdklab
2024-01-31 10:38 dpdklab
2024-01-31 10:37 dpdklab
2024-01-31 10:36 dpdklab
2024-01-31 10:36 dpdklab
2024-01-31 10:36 dpdklab
2024-01-31 10:36 dpdklab
2024-01-31 10:35 dpdklab
2024-01-31 10:28 dpdklab
2024-01-31 10:27 dpdklab
2024-01-31 10:26 dpdklab
2024-01-31 10:24 dpdklab
2024-01-31 10:24 dpdklab
2024-01-31 10:23 dpdklab
2024-01-31 10:23 dpdklab
2024-01-31 10:23 dpdklab
2024-01-31 10:22 dpdklab
2024-01-31 10:21 dpdklab
2024-01-31 10:21 dpdklab
2024-01-31 10:21 dpdklab
2024-01-31 10:19 dpdklab
2024-01-31 10:19 dpdklab
2024-01-31 10:18 dpdklab
2024-01-31 10:17 dpdklab
2024-01-31 10:16 dpdklab
2024-01-31 10:16 dpdklab
2024-01-31 10:13 dpdklab
2024-01-31 10:12 dpdklab
2024-01-31 10:12 dpdklab
2024-01-31 10:11 dpdklab
2024-01-31 10:09 dpdklab
2024-01-31 10:09 dpdklab
2024-01-31 10:08 dpdklab
2024-01-31 10:08 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=65ba25c8.810a0220.d46ee.2a3aSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
/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).