automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144058-144059 [PATCH] [v3,2/2] baseband/acc: improvement
Date: Fri, 13 Sep 2024 17:46:33 -0700 (PDT)	[thread overview]
Message-ID: <66e4dce9.050a0220.1cdf0.1e58SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240913231811.969965-3-nicolas.chautru@intel.com>

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

_Testing PASS_

Submitter: Chautru, Nicolas <nicolas.chautru@intel.com>
Date: Friday, September 13 2024 23:18:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a1114380ce5de7a9daae17e93903f7ad6566e8b6

144058-144059 --> testing pass

Upstream job id: Generic-Unit-Test-DPDK#262470

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 24.04        | PASS           |
+---------------------+----------------+
| Debian 12           | 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

CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

RHEL8
	Kernel: Depends on container host
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 22.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 24.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-14  0:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240913231811.969965-3-nicolas.chautru@intel.com>
2024-09-13 22:50 ` |SUCCESS| pw144058-144059 [PATCH v3 2/2] baseband/acc: improvement to logging mechanism qemudev
2024-09-13 22:55 ` qemudev
2024-09-13 23:19 ` |SUCCESS| pw144059 " checkpatch
2024-09-13 23:46 ` |PENDING| pw144058-144059 [PATCH] [v3,2/2] baseband/acc: improvement dpdklab
2024-09-13 23:52 ` |SUCCESS| " dpdklab
2024-09-13 23:53 ` dpdklab
2024-09-14  0:04 ` |SUCCESS| pw144059 [PATCH v3 2/2] baseband/acc: improvement to logging mechanism 0-day Robot
2024-09-14  0:10 ` |SUCCESS| pw144058-144059 [PATCH] [v3,2/2] baseband/acc: improvement dpdklab
2024-09-14  0:16 ` dpdklab
2024-09-14  0:23 ` dpdklab
2024-09-14  0:28 ` |PENDING| " dpdklab
2024-09-14  0:36 ` |SUCCESS| " dpdklab
2024-09-14  0:46 ` dpdklab [this message]
2024-09-14  0:48 ` dpdklab
2024-09-14  0:56 ` dpdklab
2024-09-14  0:57 ` dpdklab
2024-09-14  1:18 ` dpdklab
2024-09-14  2:07 ` dpdklab
2024-09-14 19:27 ` dpdklab
2024-09-14 19:39 ` dpdklab
2024-09-14 23:40 ` dpdklab
2024-09-15  2:49 ` dpdklab
2024-09-18  3:48 ` 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=66e4dce9.050a0220.1cdf0.1e58SMTPIN_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).