From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready por
Date: Fri, 01 Mar 2024 17:01:37 -0800 (PST) [thread overview]
Message-ID: <65e27a71.050a0220.73c3d.1c40SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301163931.107036-1-konstantin.v.ananyev@yandex.ru>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137690
_Testing PASS_
Submitter: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Date: Friday, March 01 2024 16:39:31
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5df34de5808a7b826b8bc035d6ee3161a12be364
137690 --> testing pass
Test environment and result as below:
+------------------+--------------------+
| Environment | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13.2 | PASS |
+------------------+--------------------+
| CentOS Stream 9 | PASS |
+------------------+--------------------+
| Debian 12 (arm) | PASS |
+------------------+--------------------+
| Fedora 37 | PASS |
+------------------+--------------------+
| CentOS Stream 8 | PASS |
+------------------+--------------------+
| openSUSE Leap 15 | PASS |
+------------------+--------------------+
| Ubuntu 22.04 | PASS |
+------------------+--------------------+
| Fedora 38 | PASS |
+------------------+--------------------+
| Ubuntu 20.04 | PASS |
+------------------+--------------------+
| RHEL8 | PASS |
+------------------+--------------------+
| Alpine | PASS |
+------------------+--------------------+
| Debian Bullseye | PASS |
+------------------+--------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29379/
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-03-02 1:01 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301163931.107036-1-konstantin.v.ananyev@yandex.ru>
2024-03-01 16:43 ` |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready port checkpatch
2024-03-01 17:44 ` 0-day Robot
2024-03-01 21:26 ` |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready por dpdklab
2024-03-01 21:32 ` |FAILURE| " dpdklab
2024-03-01 21:34 ` |SUCCESS| " dpdklab
2024-03-01 21:35 ` dpdklab
2024-03-01 21:45 ` |FAILURE| " dpdklab
2024-03-01 21:48 ` |SUCCESS| " dpdklab
2024-03-01 22:03 ` dpdklab
2024-03-01 22:20 ` |FAILURE| " dpdklab
2024-03-01 22:27 ` |SUCCESS| " dpdklab
2024-03-01 22:29 ` dpdklab
2024-03-01 22:33 ` dpdklab
2024-03-01 22:36 ` dpdklab
2024-03-01 22:37 ` dpdklab
2024-03-01 22:41 ` dpdklab
2024-03-01 22:43 ` dpdklab
2024-03-01 22:49 ` dpdklab
2024-03-01 23:21 ` dpdklab
2024-03-01 23:24 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:27 ` |FAILURE| " dpdklab
2024-03-01 23:45 ` |SUCCESS| " dpdklab
2024-03-02 0:15 ` dpdklab
2024-03-02 0:55 ` dpdklab
2024-03-02 1:01 ` dpdklab
2024-03-02 1:01 ` dpdklab [this message]
2024-03-02 1:02 ` dpdklab
2024-03-02 1:03 ` dpdklab
2024-03-02 1:03 ` dpdklab
2024-03-02 1:03 ` dpdklab
2024-03-02 1:04 ` dpdklab
2024-03-02 1:04 ` dpdklab
2024-03-02 1:04 ` dpdklab
2024-03-02 1:05 ` dpdklab
2024-03-02 1:05 ` dpdklab
2024-03-02 1:05 ` dpdklab
2024-03-02 1:06 ` dpdklab
2024-03-02 1:06 ` dpdklab
2024-03-02 1:06 ` dpdklab
2024-03-02 1:06 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:07 ` dpdklab
2024-03-02 1:08 ` dpdklab
2024-03-02 1:08 ` dpdklab
2024-03-02 1:08 ` dpdklab
2024-03-02 1:09 ` dpdklab
2024-03-02 1:09 ` dpdklab
2024-03-02 1:09 ` dpdklab
2024-03-02 1:10 ` dpdklab
2024-03-02 1:10 ` dpdklab
2024-03-02 1:10 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:11 ` dpdklab
2024-03-02 1:12 ` dpdklab
2024-03-02 1:12 ` dpdklab
2024-03-02 1:12 ` dpdklab
2024-03-02 1:18 ` dpdklab
2024-03-02 1:20 ` dpdklab
2024-03-02 1:22 ` dpdklab
2024-03-02 1:24 ` dpdklab
2024-03-02 1:24 ` dpdklab
2024-03-02 2:25 ` dpdklab
2024-03-02 2:43 ` |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready port qemudev
2024-03-02 2:48 ` qemudev
2024-03-02 4:05 ` |SUCCESS| pw137690 [PATCH] examples/l3fwd: fix Rx over not ready por dpdklab
2024-03-03 1:32 ` dpdklab
2024-03-04 6:09 ` dpdklab
2024-03-05 23:55 ` dpdklab
2024-03-06 0:27 ` dpdklab
2024-03-06 1:00 ` 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=65e27a71.050a0220.73c3d.1c40SMTPIN_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).