From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133931 [PATCH] net/cpfl: refactor flow parser
Date: Tue, 07 Nov 2023 10:06:40 -0800 (PST) [thread overview]
Message-ID: <654a7cb0.170a0220.72a4a.0a09SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133931
_Testing PASS_
Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Tuesday, November 07 2023 08:34:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2bbad8f974e00552d106c27e1d157a31179ab5ec
133931 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| Ubuntu 22.04 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28264/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-07 18:06 UTC|newest]
Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 18:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-08 5:55 dpdklab
2023-11-08 2:55 dpdklab
2023-11-07 23:45 dpdklab
2023-11-07 22:21 dpdklab
2023-11-07 22:20 dpdklab
2023-11-07 22:15 dpdklab
2023-11-07 22:15 dpdklab
2023-11-07 22:15 dpdklab
2023-11-07 22:13 dpdklab
2023-11-07 22:13 dpdklab
2023-11-07 22:12 dpdklab
2023-11-07 22:11 dpdklab
2023-11-07 22:09 dpdklab
2023-11-07 22:09 dpdklab
2023-11-07 22:09 dpdklab
2023-11-07 22:08 dpdklab
2023-11-07 22:05 dpdklab
2023-11-07 22:04 dpdklab
2023-11-07 22:03 dpdklab
2023-11-07 22:03 dpdklab
2023-11-07 22:00 dpdklab
2023-11-07 22:00 dpdklab
2023-11-07 21:30 dpdklab
2023-11-07 21:24 dpdklab
2023-11-07 21:12 dpdklab
2023-11-07 21:12 dpdklab
2023-11-07 21:12 dpdklab
2023-11-07 21:10 dpdklab
2023-11-07 20:56 dpdklab
2023-11-07 20:56 dpdklab
2023-11-07 20:40 dpdklab
2023-11-07 20:38 dpdklab
2023-11-07 20:36 dpdklab
2023-11-07 20:36 dpdklab
2023-11-07 20:36 dpdklab
2023-11-07 20:35 dpdklab
2023-11-07 20:35 dpdklab
2023-11-07 20:35 dpdklab
2023-11-07 20:35 dpdklab
2023-11-07 20:35 dpdklab
2023-11-07 20:34 dpdklab
2023-11-07 20:34 dpdklab
2023-11-07 20:33 dpdklab
2023-11-07 20:33 dpdklab
2023-11-07 20:33 dpdklab
2023-11-07 20:33 dpdklab
2023-11-07 20:31 dpdklab
2023-11-07 19:45 dpdklab
2023-11-07 19:43 dpdklab
2023-11-07 19:35 dpdklab
2023-11-07 19:33 dpdklab
2023-11-07 19:33 dpdklab
2023-11-07 19:32 dpdklab
2023-11-07 19:11 dpdklab
2023-11-07 19:10 dpdklab
2023-11-07 18:49 dpdklab
2023-11-07 18:48 dpdklab
2023-11-07 18:46 dpdklab
2023-11-07 18:46 dpdklab
2023-11-07 18:45 dpdklab
2023-11-07 18:43 dpdklab
2023-11-07 18:36 dpdklab
2023-11-07 18:20 dpdklab
2023-11-07 18:15 dpdklab
2023-11-07 18:15 dpdklab
2023-11-07 18:10 dpdklab
2023-11-07 18:09 dpdklab
2023-11-07 18:09 dpdklab
2023-11-07 18:08 dpdklab
2023-11-07 18:08 dpdklab
2023-11-07 18:06 dpdklab
2023-11-07 18:06 dpdklab
2023-11-07 18:06 dpdklab
2023-11-07 18:06 dpdklab
2023-11-07 18:06 dpdklab
2023-11-07 18:06 dpdklab
2023-11-07 18:04 dpdklab
2023-11-07 18:03 dpdklab
2023-11-07 18:03 dpdklab
2023-11-07 18:02 dpdklab
2023-11-07 18:01 dpdklab
2023-11-07 18:01 dpdklab
2023-11-07 18:00 dpdklab
2023-11-07 18:00 dpdklab
2023-11-07 17:58 dpdklab
2023-11-07 17:58 dpdklab
2023-11-07 17:57 dpdklab
2023-11-07 17:51 dpdklab
2023-11-07 17:50 dpdklab
2023-11-07 17:49 dpdklab
2023-11-07 17:49 dpdklab
2023-11-07 17:49 dpdklab
2023-11-07 17:49 dpdklab
2023-11-07 17:49 dpdklab
2023-11-07 17:48 dpdklab
2023-11-07 17:47 dpdklab
2023-11-07 17:44 dpdklab
2023-11-07 17:43 dpdklab
2023-11-07 17:43 dpdklab
2023-11-07 17:43 dpdklab
2023-11-07 17:43 dpdklab
2023-11-07 17:43 dpdklab
2023-11-07 17:41 dpdklab
2023-11-07 17:26 dpdklab
2023-11-07 17:25 dpdklab
2023-11-07 17:22 dpdklab
2023-11-07 17:16 dpdklab
2023-11-07 17:15 dpdklab
2023-11-07 17:11 dpdklab
2023-11-07 16:43 dpdklab
2023-11-07 16:34 dpdklab
2023-11-07 16:33 dpdklab
2023-11-07 16:32 dpdklab
2023-11-07 16:16 dpdklab
2023-11-07 16:16 dpdklab
2023-11-07 16:16 dpdklab
2023-11-07 16:15 dpdklab
2023-11-07 16:12 dpdklab
2023-11-07 16:12 dpdklab
2023-11-07 16:11 dpdklab
2023-11-07 16:11 dpdklab
2023-11-07 16:11 dpdklab
2023-11-07 16:11 dpdklab
2023-11-07 16:11 dpdklab
2023-11-07 16:10 dpdklab
[not found] <20231107083456.1259255-1-wenjing.qiao@intel.com>
2023-11-07 8:19 ` qemudev
2023-11-07 8:23 ` qemudev
2023-11-07 8:38 ` checkpatch
2023-11-07 10:21 ` 0-day Robot
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=654a7cb0.170a0220.72a4a.0a09SMTPIN_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).