From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143831 [PATCH] Coverity issue: Failure to enqueue packet
Date: Mon, 09 Sep 2024 23:54:41 -0700 (PDT) [thread overview]
Message-ID: <66dfed31.050a0220.46668.8624SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <tencent_78F34ED4B605837C021A9D92D6DC6A16CC05@qq.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143831
_Functional Testing PASS_
Submitter: Yong Liang <1269690261@qq.com>
Date: Monday, September 09 2024 16:57:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3
143831 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#179470
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30977/
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-09-10 6:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_78F34ED4B605837C021A9D92D6DC6A16CC05@qq.com>
2024-09-09 16:34 ` |SUCCESS| pw143831 [PATCH] Coverity issue: Failure to enqueue packets for cryptodev-scheduler_multicore can lead to program crashes Bugzilla ID: 1537 qemudev
2024-09-09 16:38 ` qemudev
2024-09-09 16:58 ` |WARNING| " checkpatch
2024-09-09 17:45 ` |SUCCESS| pw143831 [PATCH] Coverity issue: Failure to enqueue packets for cryptodev-scheduler_multicore can lead to program crashes Bugzilla ID: 1537 Fixes: replace `pending_deq_ops` with `pending_enq_ops` Cc: stable@dpdk.org 0-day Robot
2024-09-09 23:42 ` |SUCCESS| pw143831 [PATCH] Coverity issue: Failure to enqueue packet dpdklab
2024-09-09 23:46 ` dpdklab
2024-09-09 23:55 ` dpdklab
2024-09-10 0:08 ` |PENDING| " dpdklab
2024-09-10 0:11 ` |SUCCESS| " dpdklab
2024-09-10 0:33 ` |PENDING| " dpdklab
2024-09-10 2:37 ` |SUCCESS| " dpdklab
2024-09-10 3:04 ` |PENDING| " dpdklab
2024-09-10 3:45 ` |SUCCESS| " dpdklab
2024-09-10 5:31 ` dpdklab
2024-09-10 6:05 ` dpdklab
2024-09-10 6:29 ` dpdklab
2024-09-10 6:50 ` dpdklab
2024-09-10 6:54 ` dpdklab [this message]
2024-09-10 6:59 ` dpdklab
2024-09-10 7:19 ` dpdklab
2024-09-10 7:49 ` dpdklab
2024-09-10 14:50 ` dpdklab
2024-09-16 6:49 ` dpdklab
2024-09-16 13:17 ` 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=66dfed31.050a0220.46668.8624SMTPIN_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).