From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137212-137225 [PATCH] [v5,14/14] net/cnxk: fix mbuf fiel
Date: Mon, 26 Feb 2024 11:53:15 -0800 (PST) [thread overview]
Message-ID: <65dcec2b.050a0220.e08c5.45e2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137225
_Testing PASS_
Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Monday, February 26 2024 13:35:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ab5b7cd5a0b563e6d49be6c8beaad1f39c581a5c
137212-137225 --> 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 Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | 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
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29267/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-26 19:53 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 19:53 dpdklab [this message]
[not found] <20240226133536.2456406-14-ndabilpuram@marvell.com>
2024-02-28 3:04 ` dpdklab
2024-02-28 3:11 ` dpdklab
2024-02-28 3:12 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 0:00 dpdklab
2024-02-26 22:37 dpdklab
2024-02-26 22:34 dpdklab
2024-02-26 22:09 dpdklab
2024-02-26 20:54 dpdklab
2024-02-26 20:26 dpdklab
2024-02-26 20:23 dpdklab
2024-02-26 20:22 dpdklab
2024-02-26 20:20 dpdklab
2024-02-26 20:17 dpdklab
2024-02-26 20:15 dpdklab
2024-02-26 20:09 dpdklab
2024-02-26 19:56 dpdklab
2024-02-26 19:56 dpdklab
2024-02-26 19:55 dpdklab
2024-02-26 19:55 dpdklab
2024-02-26 19:53 dpdklab
2024-02-26 19:52 dpdklab
2024-02-26 19:52 dpdklab
2024-02-26 19:51 dpdklab
2024-02-26 19:50 dpdklab
2024-02-26 19:50 dpdklab
2024-02-26 19:50 dpdklab
2024-02-26 19:48 dpdklab
2024-02-26 19:46 dpdklab
2024-02-26 19:38 dpdklab
2024-02-26 19:36 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:35 dpdklab
2024-02-26 19:34 dpdklab
2024-02-26 19:34 dpdklab
2024-02-26 19:33 dpdklab
2024-02-26 19:33 dpdklab
2024-02-26 19:33 dpdklab
2024-02-26 19:32 dpdklab
2024-02-26 19:32 dpdklab
2024-02-26 19:32 dpdklab
2024-02-26 19:31 dpdklab
2024-02-26 19:27 dpdklab
2024-02-26 19:27 dpdklab
2024-02-26 19:27 dpdklab
2024-02-26 19:26 dpdklab
2024-02-26 19:25 dpdklab
2024-02-26 19:18 dpdklab
2024-02-26 19:17 dpdklab
2024-02-26 19:11 dpdklab
2024-02-26 19:11 dpdklab
2024-02-26 19:10 dpdklab
2024-02-26 19:10 dpdklab
2024-02-26 19:09 dpdklab
2024-02-26 19:09 dpdklab
2024-02-26 19:09 dpdklab
2024-02-26 19:08 dpdklab
2024-02-26 19:04 dpdklab
2024-02-26 19:03 dpdklab
2024-02-26 19:03 dpdklab
2024-02-26 19:03 dpdklab
2024-02-26 19:02 dpdklab
2024-02-26 19:02 dpdklab
2024-02-26 19:02 dpdklab
2024-02-26 19:01 dpdklab
2024-02-26 19:00 dpdklab
2024-02-26 18:57 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=65dcec2b.050a0220.e08c5.45e2SMTPIN_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).