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| pw125467-125473 [PATCH] [v2, 7/7] net/ring: replace rte atomics with GCC builtin atomics
Date: Fri, 24 Mar 2023 00:57:11 +0000 (UTC) [thread overview]
Message-ID: <20230324005711.69DDE60125@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125473
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, March 23 2023 22:34:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3223d456062bb12e9e6cf02b97966f42affa4d11
125467-125473 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25860/
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-24 0:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 0:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-25 23:43 dpdklab
2023-03-24 15:45 dpdklab
2023-03-24 2:54 dpdklab
2023-03-24 1:57 dpdklab
2023-03-24 1:20 dpdklab
2023-03-24 1:15 dpdklab
2023-03-24 1:12 dpdklab
2023-03-24 1:10 dpdklab
2023-03-24 1:05 dpdklab
2023-03-24 1:05 dpdklab
2023-03-24 1:04 dpdklab
2023-03-24 1:04 dpdklab
2023-03-24 1:04 dpdklab
[not found] <1679610881-25997-8-git-send-email-roretzla@linux.microsoft.com>
2023-03-23 22:27 ` |SUCCESS| pw125467-125473 [PATCH v2 " qemudev
2023-03-23 22:31 ` 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=20230324005711.69DDE60125@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).