From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139477 [PATCH] net/vmxnet3: fix a missing vmxnet3 regist
Date: Thu, 18 Apr 2024 01:01:11 -0700 (PDT) [thread overview]
Message-ID: <6620d347.b00a0220.c2ea5.20deSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240418055658.24500-1-ronak.doshi@broadcom.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139477
_Testing PASS_
Submitter: Ronak Doshi <ronak.doshi@broadcom.com>
Date: Thursday, April 18 2024 05:56:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ea9b0f7277acc931ced3fee4a3ee087a26ee1401
139477 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang 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
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
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.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
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Debian 12 (arm)
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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang 10.0.0-4ubuntu1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29812/
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-04-18 8:01 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240418055658.24500-1-ronak.doshi@broadcom.com>
2024-04-18 5:45 ` |SUCCESS| pw139477 [PATCH] net/vmxnet3: fix a missing vmxnet3 register command qemudev
2024-04-18 5:49 ` qemudev
2024-04-18 6:06 ` |WARNING| " checkpatch
2024-04-18 7:04 ` |SUCCESS| " 0-day Robot
2024-04-18 7:14 ` |SUCCESS| pw139477 [PATCH] net/vmxnet3: fix a missing vmxnet3 regist dpdklab
2024-04-18 7:17 ` dpdklab
2024-04-18 7:20 ` dpdklab
2024-04-18 7:20 ` dpdklab
2024-04-18 7:20 ` dpdklab
2024-04-18 7:21 ` dpdklab
2024-04-18 7:22 ` dpdklab
2024-04-18 7:23 ` dpdklab
2024-04-18 7:24 ` dpdklab
2024-04-18 7:24 ` dpdklab
2024-04-18 7:24 ` dpdklab
2024-04-18 7:30 ` dpdklab
2024-04-18 7:31 ` dpdklab
2024-04-18 7:32 ` dpdklab
2024-04-18 7:34 ` dpdklab
2024-04-18 7:34 ` dpdklab
2024-04-18 7:42 ` dpdklab
2024-04-18 7:42 ` dpdklab
2024-04-18 7:55 ` dpdklab
2024-04-18 7:56 ` dpdklab
2024-04-18 7:57 ` dpdklab
2024-04-18 7:58 ` dpdklab
2024-04-18 7:59 ` dpdklab
2024-04-18 8:00 ` dpdklab
2024-04-18 8:01 ` dpdklab [this message]
2024-04-18 8:01 ` dpdklab
2024-04-18 8:02 ` dpdklab
2024-04-18 8:03 ` dpdklab
2024-04-18 8:03 ` dpdklab
2024-04-18 8:03 ` dpdklab
2024-04-18 8:04 ` dpdklab
2024-04-18 8:04 ` dpdklab
2024-04-18 8:04 ` dpdklab
2024-04-18 8:05 ` dpdklab
2024-04-18 8:05 ` dpdklab
2024-04-18 8:05 ` dpdklab
2024-04-18 8:05 ` dpdklab
2024-04-18 8:06 ` dpdklab
2024-04-18 8:06 ` dpdklab
2024-04-18 8:06 ` dpdklab
2024-04-18 8:07 ` dpdklab
2024-04-18 8:07 ` dpdklab
2024-04-18 8:07 ` dpdklab
2024-04-18 8:07 ` dpdklab
2024-04-18 8:08 ` dpdklab
2024-04-18 8:08 ` dpdklab
2024-04-18 8:08 ` dpdklab
2024-04-18 8:09 ` dpdklab
2024-04-18 8:09 ` dpdklab
2024-04-18 8:09 ` dpdklab
2024-04-18 8:10 ` dpdklab
2024-04-18 8:10 ` dpdklab
2024-04-18 8:11 ` dpdklab
2024-04-18 8:11 ` dpdklab
2024-04-18 8:11 ` dpdklab
2024-04-18 8:12 ` dpdklab
2024-04-18 8:13 ` dpdklab
2024-04-18 8:13 ` dpdklab
2024-04-18 8:14 ` dpdklab
2024-04-18 8:15 ` dpdklab
2024-04-18 8:15 ` dpdklab
2024-04-18 8:15 ` dpdklab
2024-04-18 8:16 ` dpdklab
2024-04-18 8:16 ` dpdklab
2024-04-18 8:17 ` dpdklab
2024-04-18 8:17 ` dpdklab
2024-04-18 8:17 ` dpdklab
2024-04-18 8:18 ` dpdklab
2024-04-18 8:19 ` dpdklab
2024-04-18 8:20 ` dpdklab
2024-04-18 8:21 ` dpdklab
2024-04-18 8:22 ` dpdklab
2024-04-18 8:22 ` dpdklab
2024-04-18 8:23 ` dpdklab
2024-04-18 8:30 ` dpdklab
2024-04-18 8:36 ` dpdklab
2024-04-18 8:48 ` dpdklab
2024-04-18 9:12 ` dpdklab
2024-04-18 9:58 ` dpdklab
2024-04-18 10:09 ` dpdklab
2024-04-18 10:10 ` dpdklab
2024-04-18 10:12 ` dpdklab
2024-04-18 10:38 ` dpdklab
2024-04-18 10:53 ` dpdklab
2024-04-18 10:53 ` dpdklab
2024-04-18 12:03 ` dpdklab
2024-04-18 12:33 ` 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=6620d347.b00a0220.c2ea5.20deSMTPIN_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).