From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136207 [PATCH] [v2] app/testpmd: fix crash in multi-proc
Date: Mon, 29 Jan 2024 21:49:43 -0800 (PST) [thread overview]
Message-ID: <65b88df7.d40a0220.694e2.4f4eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136207
_Testing PASS_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Tuesday, January 30 2024 01:32:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:906d2c06b3cfc61620453c6909266fe771f8ccfb
136207 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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/28983/
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-30 5:49 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 5:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 6:55 dpdklab
2024-01-30 6:54 dpdklab
2024-01-30 6:51 dpdklab
2024-01-30 6:37 dpdklab
2024-01-30 6:36 dpdklab
2024-01-30 6:34 dpdklab
2024-01-30 6:25 dpdklab
2024-01-30 6:24 dpdklab
2024-01-30 6:23 dpdklab
2024-01-30 6:23 dpdklab
2024-01-30 6:22 dpdklab
2024-01-30 6:21 dpdklab
2024-01-30 6:21 dpdklab
2024-01-30 6:20 dpdklab
2024-01-30 6:20 dpdklab
2024-01-30 6:19 dpdklab
2024-01-30 6:19 dpdklab
2024-01-30 6:19 dpdklab
2024-01-30 6:17 dpdklab
2024-01-30 6:17 dpdklab
2024-01-30 6:17 dpdklab
2024-01-30 6:15 dpdklab
2024-01-30 6:14 dpdklab
2024-01-30 6:14 dpdklab
2024-01-30 6:13 dpdklab
2024-01-30 6:13 dpdklab
2024-01-30 6:11 dpdklab
2024-01-30 6:10 dpdklab
2024-01-30 6:09 dpdklab
2024-01-30 5:58 dpdklab
2024-01-30 5:54 dpdklab
2024-01-30 5:54 dpdklab
2024-01-30 5:53 dpdklab
2024-01-30 5:53 dpdklab
2024-01-30 5:52 dpdklab
2024-01-30 5:50 dpdklab
2024-01-30 5:50 dpdklab
2024-01-30 5:47 dpdklab
2024-01-30 5:41 dpdklab
2024-01-30 5:41 dpdklab
2024-01-30 5:40 dpdklab
2024-01-30 5:40 dpdklab
2024-01-30 5:39 dpdklab
2024-01-30 5:39 dpdklab
2024-01-30 5:38 dpdklab
2024-01-30 5:38 dpdklab
2024-01-30 5:38 dpdklab
2024-01-30 5:38 dpdklab
2024-01-30 5:38 dpdklab
2024-01-30 5:37 dpdklab
2024-01-30 5:37 dpdklab
2024-01-30 5:37 dpdklab
2024-01-30 5:36 dpdklab
2024-01-30 5:36 dpdklab
2024-01-30 5:36 dpdklab
2024-01-30 5:36 dpdklab
2024-01-30 5:35 dpdklab
2024-01-30 5:34 dpdklab
2024-01-30 5:23 dpdklab
2024-01-30 5:18 dpdklab
2024-01-30 5:17 dpdklab
2024-01-30 5:16 dpdklab
2024-01-30 5:05 dpdklab
2024-01-30 5:05 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=65b88df7.d40a0220.694e2.4f4eSMTPIN_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).