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| pw123796 [PATCH] eal/bsd: fix spinlock not unlock in alarm callback
Date: Mon, 13 Feb 2023 22:00:17 +0000 (UTC)	[thread overview]
Message-ID: <20230213220017.712136009A@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2569 bytes --]

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

_Testing PASS_

Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Monday, February 13 2023 12:44:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:39d469a7eb4f157923be73aea0b0cc1015860ca7

123796 --> testing pass

Test environment and result as below:

+-------------------------------+----------------+
|          Environment          | dpdk_unit_test |
+===============================+================+
| Ubuntu 20.04 ARM GCC Native   | PASS           |
+-------------------------------+----------------+
| Ubuntu 20.04 ARM Clang Native | PASS           |
+-------------------------------+----------------+
| Windows Server 2019           | PASS           |
+-------------------------------+----------------+
| Ubuntu 20.04                  | PASS           |
+-------------------------------+----------------+
| Ubuntu 22.04                  | PASS           |
+-------------------------------+----------------+
| CentOS Stream 9               | PASS           |
+-------------------------------+----------------+
| RHEL8                         | PASS           |
+-------------------------------+----------------+
| RHEL 7                        | PASS           |
+-------------------------------+----------------+
| openSUSE Leap 15              | PASS           |
+-------------------------------+----------------+
| Debian Bullseye               | PASS           |
+-------------------------------+----------------+


Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.1-2

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

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

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)

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-13 22:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 22:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-15 15:12 dpdklab
2023-02-14 23:22 dpdklab
2023-02-14 21:04 dpdklab
2023-02-13 22:10 dpdklab
2023-02-13 22:10 dpdklab
2023-02-13 22:03 dpdklab
2023-02-13 21:58 dpdklab
2023-02-13 21:53 dpdklab
2023-02-13 21:43 dpdklab
2023-02-13 21:41 dpdklab
2023-02-13 21:35 dpdklab
2023-02-13 21:27 dpdklab
2023-02-13 21:22 dpdklab
2023-02-13 21:15 dpdklab
2023-02-13 21:05 dpdklab
2023-02-13 14:59 dpdklab
2023-02-13 13:48 dpdklab
2023-02-13 13:41 dpdklab
2023-02-13 13:37 dpdklab
2023-02-13 13:35 dpdklab
2023-02-13 13:34 dpdklab
2023-02-13 13:33 dpdklab
2023-02-13 13:30 dpdklab
2023-02-13 13:28 dpdklab
2023-02-13 13:22 dpdklab
2023-02-13 13:17 dpdklab
2023-02-13 13:15 dpdklab
     [not found] <20230213124452.46536-1-fengchengwen@huawei.com>
2023-02-13 12:39 ` qemudev
2023-02-13 12:43 ` qemudev
2023-02-13 12:52 ` checkpatch
2023-02-14  0:39 ` 0-day Robot

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=20230213220017.712136009A@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).