From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw121822 [PATCH] [v1] examples/l3fwd: fix for coverity scan
Date: Wed, 11 Jan 2023 16:34:24 +0000 (UTC) [thread overview]
Message-ID: <20230111163424.DA96760092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4835 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/121822
_Testing PASS_
Submitter: Mohammad Iqbal Ahmad <mahmad@marvell.com>
Date: Tuesday, January 10 2023 14:56:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fe2c18a0a8b22703dec3add385a371ad819d7872
121822 --> testing pass
Test environment and result as below:
+------------------------------------+----------------+--------------------+----------------------+
| Environment | dpdk_unit_test | dpdk_meson_compile | dpdk_mingw64_compile |
+====================================+================+====================+======================+
| Ubuntu 20.04 ARM GCC Native | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM Clang Native | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS | PASS |
+------------------------------------+----------------+--------------------+----------------------+
| RHEL 7 | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| Debian Buster | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| Debian Bullseye | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| RHEL8 | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| FreeBSD 13 | SKIPPED | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | SKIPPED | PASS | SKIPPED |
+------------------------------------+----------------+--------------------+----------------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24938/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-01-11 16:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 16:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-11 16:58 dpdklab
2023-01-11 16:47 dpdklab
2023-01-11 16:36 dpdklab
2023-01-11 16:36 dpdklab
2023-01-11 16:34 dpdklab
2023-01-11 16:30 dpdklab
2023-01-11 16:27 dpdklab
2023-01-11 16:27 dpdklab
2023-01-11 16:26 dpdklab
2023-01-11 16:26 dpdklab
2023-01-11 16:25 dpdklab
2023-01-11 16:05 dpdklab
2023-01-11 15:59 dpdklab
2023-01-11 15:22 dpdklab
2023-01-11 13:12 dpdklab
2023-01-11 11:01 dpdklab
2023-01-11 10:54 dpdklab
2023-01-11 10:31 dpdklab
2023-01-11 10:24 dpdklab
2023-01-11 10:19 dpdklab
2023-01-11 10:17 dpdklab
2023-01-11 10:13 dpdklab
[not found] <20230110163442.1157560-1-mahmad@marvell.com>
2023-01-11 9:52 ` |SUCCESS| pw121822 [PATCH v1] " qemudev
2023-01-11 9:56 ` qemudev
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=20230111163424.DA96760092@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).