From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141876 [PATCH] mbuf: fix API to copy mbuf dynamic fields
Date: Wed, 26 Jun 2024 16:42:01 -0700 (PDT) [thread overview]
Message-ID: <667ca749.050a0220.90ea1.0ba9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240626120802.19333-1-sthotton@marvell.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141876
_Testing PASS_
Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Wednesday, June 26 2024 12:08:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c0fa83fe030771dea12e65ca1ba11174e1164774
141876 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Fedora 40 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 40 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 22.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 24.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Fedora 40 (ARM)
Kernel: Depends on container host
Compiler: gcc 14.1.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
Fedora 40 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6
Fedora 39 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 22.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.0
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 24.04 (ARM)
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30322/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-06-26 23:42 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240626120802.19333-1-sthotton@marvell.com>
2024-06-26 11:49 ` qemudev
2024-06-26 11:54 ` qemudev
2024-06-26 12:16 ` checkpatch
2024-06-26 13:05 ` 0-day Robot
2024-06-26 17:15 ` dpdklab
2024-06-26 17:29 ` dpdklab
2024-06-26 17:32 ` dpdklab
2024-06-26 17:36 ` dpdklab
2024-06-26 17:39 ` dpdklab
2024-06-26 17:42 ` dpdklab
2024-06-26 17:44 ` dpdklab
2024-06-26 17:49 ` dpdklab
2024-06-26 18:03 ` dpdklab
2024-06-26 18:04 ` dpdklab
2024-06-26 18:10 ` |PENDING| " dpdklab
2024-06-26 18:10 ` |SUCCESS| " dpdklab
2024-06-26 18:11 ` |PENDING| " dpdklab
2024-06-26 18:12 ` |SUCCESS| " dpdklab
2024-06-26 18:13 ` |PENDING| " dpdklab
2024-06-26 18:19 ` dpdklab
2024-06-26 18:20 ` dpdklab
2024-06-26 18:20 ` |SUCCESS| " dpdklab
2024-06-26 18:23 ` dpdklab
2024-06-26 18:26 ` dpdklab
2024-06-26 18:27 ` |PENDING| " dpdklab
2024-06-26 18:30 ` dpdklab
2024-06-26 18:33 ` |SUCCESS| " dpdklab
2024-06-26 18:33 ` |PENDING| " dpdklab
2024-06-26 18:35 ` dpdklab
2024-06-26 18:35 ` dpdklab
2024-06-26 18:38 ` dpdklab
2024-06-26 18:39 ` dpdklab
2024-06-26 18:41 ` dpdklab
2024-06-26 18:45 ` |SUCCESS| " dpdklab
2024-06-26 18:46 ` |PENDING| " dpdklab
2024-06-26 18:51 ` dpdklab
2024-06-26 19:01 ` |SUCCESS| " dpdklab
2024-06-26 19:39 ` dpdklab
2024-06-26 19:42 ` dpdklab
2024-06-26 19:47 ` dpdklab
2024-06-26 19:47 ` dpdklab
2024-06-26 19:49 ` dpdklab
2024-06-26 19:51 ` dpdklab
2024-06-26 19:52 ` dpdklab
2024-06-26 19:53 ` dpdklab
2024-06-26 19:53 ` dpdklab
2024-06-26 19:54 ` dpdklab
2024-06-26 19:54 ` dpdklab
2024-06-26 19:55 ` dpdklab
2024-06-26 19:56 ` dpdklab
2024-06-26 20:01 ` dpdklab
2024-06-26 20:03 ` dpdklab
2024-06-26 20:06 ` dpdklab
2024-06-26 20:07 ` dpdklab
2024-06-26 20:08 ` dpdklab
2024-06-26 20:09 ` dpdklab
2024-06-26 20:12 ` dpdklab
2024-06-26 20:13 ` dpdklab
2024-06-26 20:13 ` dpdklab
2024-06-26 20:15 ` dpdklab
2024-06-26 20:16 ` dpdklab
2024-06-26 20:22 ` dpdklab
2024-06-26 20:22 ` dpdklab
2024-06-26 20:22 ` dpdklab
2024-06-26 20:25 ` dpdklab
2024-06-26 20:27 ` dpdklab
2024-06-26 20:28 ` dpdklab
2024-06-26 20:29 ` dpdklab
2024-06-26 20:29 ` dpdklab
2024-06-26 20:29 ` dpdklab
2024-06-26 20:30 ` dpdklab
2024-06-26 20:30 ` dpdklab
2024-06-26 20:31 ` dpdklab
2024-06-26 20:36 ` dpdklab
2024-06-26 20:37 ` dpdklab
2024-06-26 20:37 ` dpdklab
2024-06-26 20:38 ` dpdklab
2024-06-26 20:38 ` dpdklab
2024-06-26 20:38 ` dpdklab
2024-06-26 20:45 ` dpdklab
2024-06-26 20:47 ` dpdklab
2024-06-26 20:47 ` dpdklab
2024-06-26 20:49 ` dpdklab
2024-06-26 20:56 ` dpdklab
2024-06-26 21:03 ` dpdklab
2024-06-26 21:04 ` dpdklab
2024-06-26 21:07 ` dpdklab
2024-06-26 21:08 ` dpdklab
2024-06-26 21:12 ` dpdklab
2024-06-26 21:21 ` dpdklab
2024-06-26 21:32 ` dpdklab
2024-06-26 21:34 ` dpdklab
2024-06-26 21:37 ` dpdklab
2024-06-26 21:38 ` dpdklab
2024-06-26 21:42 ` dpdklab
2024-06-26 21:44 ` dpdklab
2024-06-26 21:48 ` dpdklab
2024-06-26 21:48 ` dpdklab
2024-06-26 21:51 ` dpdklab
2024-06-26 22:06 ` dpdklab
2024-06-26 22:48 ` dpdklab
2024-06-26 22:50 ` dpdklab
2024-06-26 23:04 ` dpdklab
2024-06-26 23:08 ` dpdklab
2024-06-26 23:14 ` dpdklab
2024-06-26 23:16 ` dpdklab
2024-06-26 23:19 ` dpdklab
2024-06-26 23:19 ` dpdklab
2024-06-26 23:20 ` dpdklab
2024-06-26 23:22 ` dpdklab
2024-06-26 23:22 ` dpdklab
2024-06-26 23:40 ` dpdklab
2024-06-26 23:42 ` dpdklab [this message]
2024-06-27 2:03 ` dpdklab
2024-06-27 9:28 ` dpdklab
2024-06-27 9:45 ` dpdklab
2024-06-27 17:42 ` 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=667ca749.050a0220.90ea1.0ba9SMTPIN_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).