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: |PENDING| pw142667 [PATCH] [v1,1/1] net/ice: fix E830 PTP phy model
Date: Tue, 23 Jul 2024 13:14:44 -0700 (PDT)	[thread overview]
Message-ID: <66a00f34.5e0a0220.8b0b3.0dd7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1f6ca9415c22415fc73d7bd72f220e09b5f79025.1721740015.git.anatoly.burakov@intel.com>

Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142667

_Testing pending_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tuesday, July 23 2024 13:10:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b819d95217cd7ee707c7d059f2b5279d94a57514

142667 --> testing pending

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Debian 12           | PASS           |
+---------------------+----------------+
| Fedora 38 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Fedora 39 (Clang)   | PASS           |
+---------------------+----------------+
| Fedora 39           | PASS           |
+---------------------+----------------+
| Fedora 40           | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Fedora 40 (Clang)   | PEND           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PEND           |
+---------------------+----------------+
| RHEL9               | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PEND           |
+---------------------+----------------+
| Ubuntu 22.04        | PEND           |
+---------------------+----------------+
| Ubuntu 24.04        | PEND           |
+---------------------+----------------+
| Windows Server 2019 | PASS           |
+---------------------+----------------+


CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

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

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-23 20:14 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1f6ca9415c22415fc73d7bd72f220e09b5f79025.1721740015.git.anatoly.burakov@intel.com>
2024-07-23 12:51 ` |SUCCESS| pw142667 [PATCH v1 1/1] " qemudev
2024-07-23 12:55 ` qemudev
2024-07-23 13:12 ` checkpatch
2024-07-23 15:34 ` |SUCCESS| pw142667 [PATCH] [v1,1/1] " dpdklab
2024-07-23 15:39 ` dpdklab
2024-07-23 15:42 ` dpdklab
2024-07-23 15:43 ` dpdklab
2024-07-23 15:45 ` dpdklab
2024-07-23 15:52 ` dpdklab
2024-07-23 15:53 ` dpdklab
2024-07-23 15:55 ` dpdklab
2024-07-23 15:56 ` dpdklab
2024-07-23 15:58 ` dpdklab
2024-07-23 16:01 ` dpdklab
2024-07-23 16:41 ` dpdklab
2024-07-23 18:11 ` |PENDING| " dpdklab
2024-07-23 18:13 ` dpdklab
2024-07-23 18:16 ` dpdklab
2024-07-23 18:17 ` dpdklab
2024-07-23 18:18 ` dpdklab
2024-07-23 18:21 ` dpdklab
2024-07-23 18:22 ` dpdklab
2024-07-23 18:24 ` dpdklab
2024-07-23 18:24 ` dpdklab
2024-07-23 18:24 ` dpdklab
2024-07-23 18:25 ` dpdklab
2024-07-23 18:27 ` dpdklab
2024-07-23 18:28 ` dpdklab
2024-07-23 18:28 ` dpdklab
2024-07-23 18:29 ` dpdklab
2024-07-23 18:29 ` dpdklab
2024-07-23 18:30 ` dpdklab
2024-07-23 18:30 ` dpdklab
2024-07-23 18:33 ` dpdklab
2024-07-23 18:33 ` dpdklab
2024-07-23 18:34 ` dpdklab
2024-07-23 18:34 ` dpdklab
2024-07-23 18:36 ` dpdklab
2024-07-23 18:37 ` dpdklab
2024-07-23 18:38 ` dpdklab
2024-07-23 18:41 ` dpdklab
2024-07-23 18:42 ` dpdklab
2024-07-23 18:42 ` dpdklab
2024-07-23 18:45 ` dpdklab
2024-07-23 18:45 ` dpdklab
2024-07-23 18:49 ` dpdklab
2024-07-23 18:54 ` dpdklab
2024-07-23 18:55 ` dpdklab
2024-07-23 18:56 ` dpdklab
2024-07-23 19:05 ` |SUCCESS| " dpdklab
2024-07-23 19:06 ` dpdklab
2024-07-23 19:07 ` |PENDING| " dpdklab
2024-07-23 19:17 ` dpdklab
2024-07-23 19:21 ` dpdklab
2024-07-23 19:23 ` dpdklab
2024-07-23 19:24 ` dpdklab
2024-07-23 19:25 ` dpdklab
2024-07-23 19:30 ` dpdklab
2024-07-23 19:31 ` dpdklab
2024-07-23 19:33 ` dpdklab
2024-07-23 19:34 ` dpdklab
2024-07-23 19:37 ` dpdklab
2024-07-23 19:38 ` dpdklab
2024-07-23 19:39 ` dpdklab
2024-07-23 19:39 ` dpdklab
2024-07-23 19:41 ` dpdklab
2024-07-23 19:44 ` dpdklab
2024-07-23 19:46 ` |SUCCESS| " dpdklab
2024-07-23 19:48 ` |PENDING| " dpdklab
2024-07-23 19:50 ` |SUCCESS| " dpdklab
2024-07-23 19:54 ` dpdklab
2024-07-23 19:57 ` |PENDING| " dpdklab
2024-07-23 19:58 ` dpdklab
2024-07-23 20:00 ` dpdklab
2024-07-23 20:01 ` dpdklab
2024-07-23 20:04 ` dpdklab
2024-07-23 20:11 ` dpdklab
2024-07-23 20:13 ` |SUCCESS| " dpdklab
2024-07-23 20:14 ` dpdklab [this message]
2024-07-23 20:17 ` |PENDING| " dpdklab
2024-07-23 20:17 ` dpdklab
2024-07-23 20:22 ` dpdklab
2024-07-23 20:22 ` dpdklab
2024-07-23 20:24 ` |SUCCESS| " dpdklab
2024-07-23 20:29 ` |PENDING| " dpdklab
2024-07-23 20:35 ` dpdklab
2024-07-23 20:36 ` dpdklab
2024-07-23 20:36 ` |SUCCESS| " dpdklab
2024-07-23 20:39 ` |PENDING| " dpdklab
2024-07-23 20:44 ` dpdklab
2024-07-23 20:44 ` dpdklab
2024-07-23 20:48 ` dpdklab
2024-07-23 20:49 ` dpdklab
2024-07-23 20:50 ` dpdklab
2024-07-23 20:50 ` dpdklab
2024-07-23 20:50 ` dpdklab
2024-07-23 20:53 ` dpdklab
2024-07-23 20:54 ` dpdklab
2024-07-23 20:55 ` dpdklab
2024-07-23 20:57 ` dpdklab
2024-07-23 20:57 ` dpdklab
2024-07-23 20:58 ` dpdklab
2024-07-23 21:00 ` |SUCCESS| " dpdklab
2024-07-23 21:01 ` dpdklab
2024-07-23 21:02 ` |PENDING| " dpdklab
2024-07-23 21:06 ` dpdklab
2024-07-23 21:07 ` dpdklab
2024-07-23 21:11 ` dpdklab
2024-07-23 21:14 ` dpdklab
2024-07-23 21:16 ` dpdklab
2024-07-23 21:24 ` dpdklab
2024-07-24 20:16 ` |SUCCESS| " 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=66a00f34.5e0a0220.8b0b3.0dd7SMTPIN_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).