From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141130 [PATCH] [v4] net/mana: fix uninitialized scalar v
Date: Thu, 13 Jun 2024 14:09:49 -0700 (PDT) [thread overview]
Message-ID: <666b601d.170a0220.9ecde.568dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240613183040.865732-1-mahmoudmatook.mm@gmail.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141130
_Testing PASS_
Submitter: Mahmoud Maatuq <mahmoudmatook.mm@gmail.com>
Date: Thursday, June 13 2024 18:30:39
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fbba6db3640f9f623c29c452e1a6b057073e81d2
141130 --> testing pass
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Debian 12 with MUSDK | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+--------------------+
| RHEL9 (ARM) | PASS |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+--------------------------+--------------------+
| Ubuntu 24.04 (ARM) | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------+--------------------+
| Debian 12 (arm) | PASS |
+--------------------------+--------------------+
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
RHEL9 (ARM)
Kernel: Depends on container host
Compiler: gcc 11.4.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.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
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30184/
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-13 21:09 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240613183040.865732-1-mahmoudmatook.mm@gmail.com>
2024-06-13 18:07 ` |SUCCESS| pw141130 [PATCH v4] net/mana: fix uninitialized scalar variable qemudev
2024-06-13 18:11 ` qemudev
2024-06-13 18:31 ` checkpatch
2024-06-13 19:24 ` 0-day Robot
2024-06-13 20:56 ` |SUCCESS| pw141130 [PATCH] [v4] net/mana: fix uninitialized scalar v dpdklab
2024-06-13 20:57 ` dpdklab
2024-06-13 20:57 ` dpdklab
2024-06-13 20:57 ` dpdklab
2024-06-13 20:58 ` dpdklab
2024-06-13 20:58 ` dpdklab
2024-06-13 20:58 ` dpdklab
2024-06-13 20:59 ` dpdklab
2024-06-13 20:59 ` dpdklab
2024-06-13 20:59 ` dpdklab
2024-06-13 20:59 ` dpdklab
2024-06-13 21:00 ` dpdklab
2024-06-13 21:00 ` dpdklab
2024-06-13 21:00 ` dpdklab
2024-06-13 21:01 ` dpdklab
2024-06-13 21:01 ` dpdklab
2024-06-13 21:02 ` dpdklab
2024-06-13 21:02 ` dpdklab
2024-06-13 21:02 ` dpdklab
2024-06-13 21:03 ` dpdklab
2024-06-13 21:03 ` dpdklab
2024-06-13 21:03 ` dpdklab
2024-06-13 21:03 ` dpdklab
2024-06-13 21:04 ` dpdklab
2024-06-13 21:04 ` dpdklab
2024-06-13 21:05 ` dpdklab
2024-06-13 21:05 ` dpdklab
2024-06-13 21:05 ` dpdklab
2024-06-13 21:06 ` dpdklab
2024-06-13 21:06 ` dpdklab
2024-06-13 21:06 ` dpdklab
2024-06-13 21:07 ` dpdklab
2024-06-13 21:07 ` dpdklab
2024-06-13 21:08 ` dpdklab
2024-06-13 21:09 ` dpdklab
2024-06-13 21:09 ` dpdklab [this message]
2024-06-13 21:10 ` dpdklab
2024-06-13 21:11 ` dpdklab
2024-06-13 21:11 ` dpdklab
2024-06-13 21:12 ` dpdklab
2024-06-13 21:12 ` dpdklab
2024-06-13 21:13 ` dpdklab
2024-06-13 21:13 ` dpdklab
2024-06-13 21:14 ` dpdklab
2024-06-13 21:14 ` dpdklab
2024-06-13 21:14 ` dpdklab
2024-06-13 21:15 ` dpdklab
2024-06-13 21:15 ` dpdklab
2024-06-13 21:15 ` dpdklab
2024-06-13 21:16 ` dpdklab
2024-06-13 21:17 ` dpdklab
2024-06-13 21:17 ` dpdklab
2024-06-13 21:19 ` dpdklab
2024-06-13 21:19 ` dpdklab
2024-06-13 21:19 ` dpdklab
2024-06-13 21:22 ` dpdklab
2024-06-13 21:22 ` dpdklab
2024-06-13 21:22 ` dpdklab
2024-06-13 21:23 ` dpdklab
2024-06-13 21:23 ` dpdklab
2024-06-13 21:25 ` dpdklab
2024-06-13 21:25 ` dpdklab
2024-06-13 21:27 ` dpdklab
2024-06-13 21:27 ` dpdklab
2024-06-13 21:27 ` dpdklab
2024-06-13 21:27 ` dpdklab
2024-06-13 21:31 ` dpdklab
2024-06-13 21:31 ` dpdklab
2024-06-13 21:31 ` dpdklab
2024-06-13 21:32 ` dpdklab
2024-06-13 21:34 ` dpdklab
2024-06-13 21:35 ` dpdklab
2024-06-13 21:37 ` dpdklab
2024-06-13 21:38 ` dpdklab
2024-06-13 21:45 ` dpdklab
2024-06-13 21:46 ` dpdklab
2024-06-13 21:46 ` dpdklab
2024-06-13 21:46 ` dpdklab
2024-06-13 21:46 ` dpdklab
2024-06-13 21:46 ` dpdklab
2024-06-13 21:47 ` dpdklab
2024-06-13 21:48 ` dpdklab
2024-06-13 21:49 ` dpdklab
2024-06-13 21:49 ` dpdklab
2024-06-13 21:49 ` dpdklab
2024-06-13 21:49 ` dpdklab
2024-06-13 21:49 ` dpdklab
2024-06-13 22:05 ` dpdklab
2024-06-13 22:05 ` dpdklab
2024-06-13 22:17 ` dpdklab
2024-06-13 22:17 ` dpdklab
2024-06-13 22:18 ` dpdklab
2024-06-13 22:20 ` dpdklab
2024-06-13 22:22 ` dpdklab
2024-06-13 22:23 ` dpdklab
2024-06-13 22:23 ` dpdklab
2024-06-13 22:26 ` dpdklab
2024-06-13 22:26 ` 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=666b601d.170a0220.9ecde.568dSMTPIN_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).