From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142838 [PATCH] examples/eventdev: fix segment fault with
Date: Thu, 01 Aug 2024 13:38:20 -0700 (PDT) [thread overview]
Message-ID: <66abf23c.050a0220.2151b2.01bfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240801111120.5380-1-fengchengwen@huawei.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142838
_Functional Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Thursday, August 01 2024 11:11:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084
142838 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#172495
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30697/
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-08-01 20:38 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240801111120.5380-1-fengchengwen@huawei.com>
2024-08-01 10:47 ` |SUCCESS| pw142838 [PATCH] examples/eventdev: fix segment fault with generic pipeline qemudev
2024-08-01 10:52 ` qemudev
2024-08-01 11:16 ` |WARNING| " checkpatch
2024-08-01 16:42 ` |SUCCESS| " 0-day Robot
2024-08-01 19:41 ` |SUCCESS| pw142838 [PATCH] examples/eventdev: fix segment fault with dpdklab
2024-08-01 20:25 ` |PENDING| " dpdklab
2024-08-01 20:33 ` dpdklab
2024-08-01 20:38 ` dpdklab [this message]
2024-08-01 20:38 ` dpdklab
2024-08-01 20:46 ` |SUCCESS| " dpdklab
2024-08-01 20:48 ` |PENDING| " dpdklab
2024-08-01 20:51 ` dpdklab
2024-08-01 20:54 ` dpdklab
2024-08-01 20:55 ` dpdklab
2024-08-01 20:56 ` dpdklab
2024-08-01 20:56 ` dpdklab
2024-08-01 21:00 ` dpdklab
2024-08-01 21:02 ` |SUCCESS| " dpdklab
2024-08-01 21:02 ` |PENDING| " dpdklab
2024-08-01 21:03 ` dpdklab
2024-08-01 21:05 ` dpdklab
2024-08-01 21:09 ` |SUCCESS| " dpdklab
2024-08-01 21:09 ` dpdklab
2024-08-01 21:09 ` dpdklab
2024-08-01 22:07 ` |PENDING| " dpdklab
2024-08-01 22:15 ` |SUCCESS| " dpdklab
2024-08-01 22:15 ` dpdklab
2024-08-01 22:18 ` |PENDING| " dpdklab
2024-08-01 22:19 ` dpdklab
2024-08-01 22:20 ` |SUCCESS| " dpdklab
2024-08-01 22:21 ` |PENDING| " dpdklab
2024-08-01 22:23 ` |SUCCESS| " dpdklab
2024-08-01 22:23 ` dpdklab
2024-08-01 22:24 ` dpdklab
2024-08-01 22:25 ` dpdklab
2024-08-01 22:29 ` dpdklab
2024-08-01 22:33 ` |PENDING| " dpdklab
2024-08-01 22:36 ` dpdklab
2024-08-01 22:49 ` |SUCCESS| " dpdklab
2024-08-01 22:50 ` dpdklab
2024-08-01 22:55 ` dpdklab
2024-08-01 23:14 ` |PENDING| " dpdklab
2024-08-01 23:58 ` dpdklab
2024-08-02 0:37 ` dpdklab
2024-08-02 0:40 ` dpdklab
2024-08-02 0:45 ` dpdklab
2024-08-02 0:47 ` dpdklab
2024-08-02 0:48 ` dpdklab
2024-08-02 0:50 ` dpdklab
2024-08-02 0:54 ` dpdklab
2024-08-02 0:55 ` dpdklab
2024-08-02 0:56 ` dpdklab
2024-08-02 0:57 ` dpdklab
2024-08-02 0:59 ` dpdklab
2024-08-02 1:01 ` dpdklab
2024-08-02 1:03 ` dpdklab
2024-08-02 1:03 ` dpdklab
2024-08-02 1:03 ` dpdklab
2024-08-02 1:04 ` dpdklab
2024-08-02 1:06 ` dpdklab
2024-08-02 1:09 ` dpdklab
2024-08-02 1:09 ` dpdklab
2024-08-02 1:09 ` dpdklab
2024-08-02 1:10 ` dpdklab
2024-08-02 1:10 ` dpdklab
2024-08-02 1:13 ` dpdklab
2024-08-02 1:14 ` dpdklab
2024-08-02 1:15 ` dpdklab
2024-08-02 1:15 ` dpdklab
2024-08-02 1:17 ` dpdklab
2024-08-02 1:18 ` dpdklab
2024-08-02 1:18 ` dpdklab
2024-08-02 1:18 ` dpdklab
2024-08-02 1:20 ` dpdklab
2024-08-02 1:23 ` dpdklab
2024-08-02 1:24 ` dpdklab
2024-08-02 1:26 ` |SUCCESS| " dpdklab
2024-08-02 1:28 ` dpdklab
2024-08-02 1:28 ` |PENDING| " dpdklab
2024-08-02 1:28 ` dpdklab
2024-08-02 1:31 ` dpdklab
2024-08-02 1:35 ` dpdklab
2024-08-02 1:38 ` dpdklab
2024-08-02 1:38 ` dpdklab
2024-08-02 1:40 ` dpdklab
2024-08-02 1:54 ` |SUCCESS| " dpdklab
2024-08-02 2:05 ` |PENDING| " dpdklab
2024-08-02 2:10 ` dpdklab
2024-08-02 2:15 ` dpdklab
2024-08-02 2:17 ` dpdklab
2024-08-02 2:17 ` dpdklab
2024-08-02 2:23 ` dpdklab
2024-08-02 2:26 ` dpdklab
2024-08-02 2:27 ` dpdklab
2024-08-02 2:29 ` dpdklab
2024-08-02 2:31 ` dpdklab
2024-08-02 2:32 ` dpdklab
2024-08-02 2:34 ` dpdklab
2024-08-02 2:36 ` dpdklab
2024-08-02 2:36 ` dpdklab
2024-08-02 2:38 ` dpdklab
2024-08-02 2:40 ` dpdklab
2024-08-02 2:40 ` dpdklab
2024-08-02 2:42 ` dpdklab
2024-08-02 2:44 ` dpdklab
2024-08-02 2:48 ` dpdklab
2024-08-02 2:55 ` |SUCCESS| " dpdklab
2024-08-02 2:55 ` dpdklab
2024-08-02 3:18 ` dpdklab
2024-08-03 2:04 ` dpdklab
2024-08-06 4:09 ` dpdklab
2024-08-06 4:18 ` dpdklab
2024-08-06 4:32 ` 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=66abf23c.050a0220.2151b2.01bfSMTPIN_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).