From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Dengdui Huang <huangdengdui@huawei.com>
Subject: |SUCCESS| pw136170 [PATCH] app/testpmd: fix crash in multi-process p
Date: Thu, 25 Jan 2024 20:10:54 -0800 (PST) [thread overview]
Message-ID: <65b330ce.020a0220.ac732.0f01SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136170
_Testing PASS_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Friday, January 26 2024 02:41:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6676a3793b4292baf606092a8e3e14ea67550c58
136170 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28969/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-26 4:10 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 4:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-26 6:23 dpdklab
2024-01-26 5:08 dpdklab
2024-01-26 4:43 dpdklab
2024-01-26 4:34 dpdklab
2024-01-26 4:34 dpdklab
2024-01-26 4:31 dpdklab
2024-01-26 4:30 dpdklab
2024-01-26 4:22 dpdklab
2024-01-26 4:21 dpdklab
2024-01-26 4:19 dpdklab
2024-01-26 4:19 dpdklab
2024-01-26 4:17 dpdklab
2024-01-26 4:17 dpdklab
2024-01-26 4:14 dpdklab
2024-01-26 4:05 dpdklab
2024-01-26 4:04 dpdklab
2024-01-26 4:02 dpdklab
2024-01-26 4:00 dpdklab
2024-01-26 3:51 dpdklab
2024-01-26 3:47 dpdklab
2024-01-26 3:41 dpdklab
2024-01-26 3:41 dpdklab
2024-01-26 3:40 dpdklab
2024-01-26 3:39 dpdklab
2024-01-26 3:39 dpdklab
2024-01-26 3:38 dpdklab
2024-01-26 3:37 dpdklab
2024-01-26 3:36 dpdklab
2024-01-26 3:36 dpdklab
2024-01-26 3:34 dpdklab
2024-01-26 3:32 dpdklab
2024-01-26 3:30 dpdklab
2024-01-26 3:30 dpdklab
2024-01-26 3:28 dpdklab
2024-01-26 3:27 dpdklab
2024-01-26 3:27 dpdklab
2024-01-26 3:27 dpdklab
2024-01-26 3:25 dpdklab
2024-01-26 3:25 dpdklab
2024-01-26 3:23 dpdklab
2024-01-26 3:23 dpdklab
2024-01-26 3:23 dpdklab
2024-01-26 3:22 dpdklab
2024-01-26 3:21 dpdklab
2024-01-26 3:21 dpdklab
2024-01-26 3:20 dpdklab
2024-01-26 3:19 dpdklab
2024-01-26 3:19 dpdklab
2024-01-26 3:19 dpdklab
2024-01-26 3:19 dpdklab
2024-01-26 3:18 dpdklab
2024-01-26 3:18 dpdklab
2024-01-26 3:18 dpdklab
2024-01-26 3:18 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=65b330ce.020a0220.ac732.0f01SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=huangdengdui@huawei.com \
--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).