automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125479-125480 [PATCH] [v3, 7/7] net/ring: replace rte atomics with GCC builtin atomics
Date: Sun, 26 Mar 2023 00:26:40 +0000 (UTC)	[thread overview]
Message-ID: <20230326002640.959B760095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125480

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thursday, March 23 2023 22:53:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3223d456062bb12e9e6cf02b97966f42affa4d11

125479-125480 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Debian Buster    | PASS           |
+------------------+----------------+
| Ubuntu 22.04     | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | PASS           |
+------------------+----------------+
| RHEL 7           | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+
| RHEL8            | PASS           |
+------------------+----------------+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| CentOS Stream 9  | PASS           |
+------------------+----------------+


Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25861/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-03-26  0:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26  0:26 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-24 15:53 dpdklab
2023-03-24  3:45 dpdklab
2023-03-24  3:00 dpdklab
2023-03-24  2:13 dpdklab
2023-03-24  2:08 dpdklab
2023-03-24  2:03 dpdklab
2023-03-24  2:03 dpdklab
2023-03-24  1:58 dpdklab
2023-03-24  1:58 dpdklab
2023-03-24  1:56 dpdklab
2023-03-24  1:55 dpdklab
2023-03-24  1:51 dpdklab
2023-03-24  1:45 dpdklab
     [not found] <1679612036-30773-8-git-send-email-roretzla@linux.microsoft.com>
2023-03-23 22:47 ` |SUCCESS| pw125479-125480 [PATCH v3 " qemudev
2023-03-23 22:51 ` 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=20230326002640.959B760095@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --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).