From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143959 [PATCH] crypto/scheduler: fix crashes in schedule
Date: Wed, 11 Sep 2024 20:12:26 -0700 (PDT) [thread overview]
Message-ID: <66e25c1a.170a0220.34ca5f.3e75SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <tencent_98734034A30594BC001A8912CB3C7ED6CF05@qq.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143959
_Testing PASS_
Submitter: Yong Liang <1269690261@qq.com>
Date: Wednesday, September 11 2024 16:06:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3
143959 --> testing pass
Upstream job id: Generic-VM-Unit-Test-DPDK#25214
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS |
+---------------------+----------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31004/
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-12 3:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_98734034A30594BC001A8912CB3C7ED6CF05@qq.com>
2024-09-11 16:05 ` |SUCCESS| pw143959 [PATCH] crypto/scheduler: fix crashes in scheduler_multicore due to incorrect variable usage qemudev
2024-09-11 16:07 ` checkpatch
2024-09-11 16:10 ` qemudev
2024-09-11 17:05 ` 0-day Robot
2024-09-11 22:30 ` |SUCCESS| pw143959 [PATCH] crypto/scheduler: fix crashes in schedule dpdklab
2024-09-11 22:44 ` dpdklab
2024-09-11 22:45 ` dpdklab
2024-09-11 23:11 ` dpdklab
2024-09-11 23:41 ` dpdklab
2024-09-11 23:41 ` dpdklab
2024-09-12 0:31 ` dpdklab
2024-09-12 1:19 ` dpdklab
2024-09-12 1:44 ` |PENDING| " dpdklab
2024-09-12 1:51 ` |SUCCESS| " dpdklab
2024-09-12 1:51 ` dpdklab
2024-09-12 2:04 ` |PENDING| " dpdklab
2024-09-12 2:33 ` |SUCCESS| " dpdklab
2024-09-12 2:34 ` dpdklab
2024-09-12 2:46 ` dpdklab
2024-09-12 2:48 ` dpdklab
2024-09-12 3:01 ` |PENDING| " dpdklab
2024-09-12 3:12 ` dpdklab [this message]
2024-09-12 3:13 ` |SUCCESS| " dpdklab
2024-09-12 3:18 ` dpdklab
2024-09-12 3:23 ` dpdklab
2024-09-12 3:23 ` dpdklab
2024-09-12 3:24 ` |PENDING| " dpdklab
2024-09-12 3:43 ` |SUCCESS| " dpdklab
2024-09-12 3:43 ` dpdklab
2024-09-12 3:50 ` dpdklab
2024-09-12 3:58 ` dpdklab
2024-09-12 4:10 ` dpdklab
2024-09-12 4:28 ` dpdklab
2024-09-12 4:40 ` dpdklab
2024-09-12 4:43 ` dpdklab
2024-09-12 4:45 ` dpdklab
2024-09-12 4:50 ` dpdklab
2024-09-12 5:10 ` dpdklab
2024-09-12 6:13 ` dpdklab
2024-09-12 9:05 ` dpdklab
2024-09-12 13:15 ` dpdklab
2024-09-12 14:06 ` dpdklab
2024-09-15 12:44 ` dpdklab
2024-09-15 13:09 ` dpdklab
2024-09-15 17:49 ` dpdklab
2024-09-15 18:19 ` 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=66e25c1a.170a0220.34ca5f.3e75SMTPIN_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).