From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131951-131962 [PATCH] [v6,12/12] app/graph: add l3fwd us
Date: Tue, 26 Sep 2023 12:29:23 -0700 (PDT) [thread overview]
Message-ID: <65133113.920a0220.1ed51.a493SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131962
_Testing PASS_
Submitter: Sunil Kumar Kori <skori@marvell.com>
Date: Tuesday, September 26 2023 10:57:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d58c97481a136ad5342c9d8717b22bdaa5eccd43
131951-131962 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27729/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-26 19:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 19:29 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 2:01 dpdklab
2023-09-26 20:26 dpdklab
2023-09-26 20:18 dpdklab
2023-09-26 20:15 dpdklab
2023-09-26 20:13 dpdklab
2023-09-26 20:12 dpdklab
2023-09-26 20:10 dpdklab
2023-09-26 19:55 dpdklab
2023-09-26 19:50 dpdklab
2023-09-26 19:50 dpdklab
2023-09-26 19:46 dpdklab
2023-09-26 19:45 dpdklab
2023-09-26 19:43 dpdklab
2023-09-26 19:41 dpdklab
2023-09-26 19:41 dpdklab
2023-09-26 19:40 dpdklab
2023-09-26 19:38 dpdklab
2023-09-26 19:35 dpdklab
2023-09-26 19:35 dpdklab
2023-09-26 19:30 dpdklab
2023-09-26 19:21 dpdklab
2023-09-26 19:02 dpdklab
2023-09-26 18:59 dpdklab
2023-09-26 18:45 dpdklab
2023-09-26 18:37 dpdklab
2023-09-26 18:36 dpdklab
2023-09-26 18:34 dpdklab
2023-09-26 18:33 dpdklab
2023-09-26 18:31 dpdklab
2023-09-26 18:30 dpdklab
2023-09-26 18:11 dpdklab
2023-09-26 17:55 dpdklab
2023-09-26 17:48 dpdklab
2023-09-26 17:48 dpdklab
2023-09-26 17:47 dpdklab
2023-09-26 17:44 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=65133113.920a0220.1ed51.a493SMTPIN_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).