From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139761-139769 [PATCH] [v10,9/9] net/tap: update document
Date: Wed, 01 May 2024 11:06:30 -0700 (PDT) [thread overview]
Message-ID: <663284a6.c80a0220.5e1a6.d8ccSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240501161403.114658-10-stephen@networkplumber.org>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139769
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, May 01 2024 16:12:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139761-139769 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang 10.0.0-4ubuntu1
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
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29888/
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-05-01 18:06 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240501161403.114658-10-stephen@networkplumber.org>
2024-05-01 15:50 ` |SUCCESS| pw139761-139769 [PATCH v10 9/9] net/tap: update documentation qemudev
2024-05-01 15:54 ` qemudev
2024-05-01 17:03 ` |SUCCESS| pw139769 " 0-day Robot
2024-05-01 17:31 ` |SUCCESS| pw139761-139769 [PATCH] [v10,9/9] net/tap: update document dpdklab
2024-05-01 17:32 ` dpdklab
2024-05-01 17:32 ` dpdklab
2024-05-01 17:33 ` dpdklab
2024-05-01 17:34 ` dpdklab
2024-05-01 17:36 ` dpdklab
2024-05-01 17:45 ` dpdklab
2024-05-01 17:46 ` dpdklab
2024-05-01 17:47 ` dpdklab
2024-05-01 17:49 ` dpdklab
2024-05-01 17:50 ` dpdklab
2024-05-01 17:51 ` dpdklab
2024-05-01 17:51 ` dpdklab
2024-05-01 17:51 ` dpdklab
2024-05-01 17:52 ` dpdklab
2024-05-01 17:52 ` dpdklab
2024-05-01 17:52 ` dpdklab
2024-05-01 17:53 ` dpdklab
2024-05-01 17:53 ` dpdklab
2024-05-01 17:54 ` dpdklab
2024-05-01 17:55 ` dpdklab
2024-05-01 17:56 ` dpdklab
2024-05-01 17:56 ` dpdklab
2024-05-01 17:56 ` dpdklab
2024-05-01 17:57 ` dpdklab
2024-05-01 17:57 ` dpdklab
2024-05-01 17:58 ` dpdklab
2024-05-01 17:58 ` dpdklab
2024-05-01 17:58 ` dpdklab
2024-05-01 17:59 ` dpdklab
2024-05-01 17:59 ` dpdklab
2024-05-01 17:59 ` dpdklab
2024-05-01 18:00 ` dpdklab
2024-05-01 18:00 ` dpdklab
2024-05-01 18:00 ` dpdklab
2024-05-01 18:00 ` dpdklab
2024-05-01 18:01 ` dpdklab
2024-05-01 18:01 ` dpdklab
2024-05-01 18:02 ` dpdklab
2024-05-01 18:02 ` dpdklab
2024-05-01 18:02 ` dpdklab
2024-05-01 18:03 ` dpdklab
2024-05-01 18:03 ` dpdklab
2024-05-01 18:03 ` dpdklab
2024-05-01 18:04 ` dpdklab
2024-05-01 18:05 ` dpdklab
2024-05-01 18:05 ` dpdklab
2024-05-01 18:05 ` dpdklab
2024-05-01 18:06 ` dpdklab
2024-05-01 18:06 ` dpdklab
2024-05-01 18:06 ` dpdklab [this message]
2024-05-01 18:07 ` dpdklab
2024-05-01 18:07 ` dpdklab
2024-05-01 18:07 ` dpdklab
2024-05-01 18:08 ` dpdklab
2024-05-01 18:08 ` dpdklab
2024-05-01 18:08 ` dpdklab
2024-05-01 18:09 ` dpdklab
2024-05-01 18:09 ` dpdklab
2024-05-01 18:09 ` dpdklab
2024-05-01 18:09 ` dpdklab
2024-05-01 18:10 ` dpdklab
2024-05-01 18:10 ` dpdklab
2024-05-01 18:10 ` dpdklab
2024-05-01 18:10 ` dpdklab
2024-05-01 18:14 ` dpdklab
2024-05-01 18:14 ` dpdklab
2024-05-01 18:17 ` dpdklab
2024-05-01 18:17 ` dpdklab
2024-05-01 18:21 ` dpdklab
2024-05-01 18:25 ` dpdklab
2024-05-01 18:34 ` dpdklab
2024-05-01 18:35 ` dpdklab
2024-05-01 19:06 ` dpdklab
2024-05-01 19:08 ` dpdklab
2024-05-01 19:12 ` dpdklab
2024-05-04 0:42 ` dpdklab
2024-05-04 13:40 ` dpdklab
2024-05-04 13:44 ` dpdklab
2024-05-04 13:48 ` dpdklab
2024-05-04 13:52 ` dpdklab
2024-05-04 14:27 ` dpdklab
2024-05-06 5:56 ` 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=663284a6.c80a0220.5e1a6.d8ccSMTPIN_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).