From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124620-124631 [PATCH] [17/17] test-eventdev: use previous value atomic fetch operations
Date: Thu, 2 Mar 2023 04:21:38 +0000 (UTC) [thread overview]
Message-ID: <20230302042138.DC1C0601F7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124631
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, March 02 2023 00:47:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124620-124631 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25582/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-02 4:21 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 4:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-04 1:32 dpdklab
2023-03-04 1:31 dpdklab
2023-03-04 1:11 dpdklab
2023-03-04 1:07 dpdklab
2023-03-04 1:02 dpdklab
2023-03-04 1:01 dpdklab
2023-03-04 1:01 dpdklab
2023-03-04 0:58 dpdklab
2023-03-04 0:55 dpdklab
2023-03-04 0:34 dpdklab
2023-03-04 0:32 dpdklab
2023-03-04 0:26 dpdklab
2023-03-04 0:25 dpdklab
2023-03-04 0:19 dpdklab
2023-03-04 0:19 dpdklab
2023-03-04 0:18 dpdklab
2023-03-03 23:46 dpdklab
2023-03-03 23:44 dpdklab
2023-03-03 23:40 dpdklab
2023-03-03 23:39 dpdklab
2023-03-03 23:38 dpdklab
2023-03-03 23:37 dpdklab
2023-03-03 23:35 dpdklab
2023-03-03 23:24 dpdklab
2023-03-03 23:20 dpdklab
2023-03-03 23:17 dpdklab
2023-03-03 23:15 dpdklab
2023-03-03 23:10 dpdklab
2023-03-02 23:28 dpdklab
2023-03-02 22:48 dpdklab
2023-03-02 17:00 dpdklab
2023-03-02 16:14 dpdklab
2023-03-02 11:36 dpdklab
2023-03-02 11:16 dpdklab
2023-03-02 11:04 dpdklab
2023-03-02 10:51 dpdklab
2023-03-02 10:16 dpdklab
2023-03-02 10:04 dpdklab
2023-03-02 9:48 dpdklab
2023-03-02 9:35 dpdklab
2023-03-02 6:17 dpdklab
2023-03-02 6:10 dpdklab
2023-03-02 6:04 dpdklab
2023-03-02 5:48 dpdklab
2023-03-02 5:12 dpdklab
2023-03-02 5:00 dpdklab
2023-03-02 4:52 dpdklab
2023-03-02 4:46 dpdklab
2023-03-02 4:46 dpdklab
2023-03-02 4:44 dpdklab
2023-03-02 4:44 dpdklab
2023-03-02 4:41 dpdklab
2023-03-02 4:29 dpdklab
2023-03-02 4:25 dpdklab
2023-03-02 4:18 dpdklab
2023-03-02 3:07 dpdklab
2023-03-02 2:53 dpdklab
[not found] <1677718068-2412-18-git-send-email-roretzla@linux.microsoft.com>
2023-03-02 0:42 ` |SUCCESS| pw124620-124631 [PATCH 17/17] " qemudev
2023-03-02 0:46 ` qemudev
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=20230302042138.DC1C0601F7@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).