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| pw142749 [PATCH] [v24.11,v1] net/sfc: allow for use of ind
Date: Mon, 29 Jul 2024 14:39:05 -0700 (PDT)	[thread overview]
Message-ID: <66a80bf9.050a0220.2ab814.a59fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240729163847.7261-1-ivan.malov@arknetworks.am>

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

_Testing pending_

Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Monday, July 29 2024 16:38:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3e440dd0ecf47f19716503374610ddd75d3a5ce9

142749 --> testing pending

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

Test environment and result as below:

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


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

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

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

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

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

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

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

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

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

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

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

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

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.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

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

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-29 21:39 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240729163847.7261-1-ivan.malov@arknetworks.am>
2024-07-29 16:12 ` |SUCCESS| pw142749 [v24.11 PATCH v1] net/sfc: allow for use of indirect counter in tunnel offload qemudev
2024-07-29 16:16 ` qemudev
2024-07-29 16:40 ` |WARNING| " checkpatch
2024-07-29 17:42 ` |SUCCESS| " 0-day Robot
2024-07-29 20:00 ` |PENDING| pw142749 [PATCH] [v24.11,v1] net/sfc: allow for use of ind dpdklab
2024-07-29 20:05 ` |SUCCESS| " dpdklab
2024-07-29 20:05 ` |PENDING| " dpdklab
2024-07-29 20:07 ` |SUCCESS| " dpdklab
2024-07-29 20:08 ` dpdklab
2024-07-29 20:11 ` dpdklab
2024-07-29 20:13 ` |PENDING| " dpdklab
2024-07-29 20:14 ` dpdklab
2024-07-29 20:15 ` |SUCCESS| " dpdklab
2024-07-29 20:18 ` dpdklab
2024-07-29 20:20 ` |PENDING| " dpdklab
2024-07-29 20:21 ` dpdklab
2024-07-29 20:21 ` dpdklab
2024-07-29 20:22 ` |SUCCESS| " dpdklab
2024-07-29 20:22 ` |PENDING| " dpdklab
2024-07-29 20:23 ` dpdklab
2024-07-29 20:23 ` |SUCCESS| " dpdklab
2024-07-29 20:24 ` |PENDING| " dpdklab
2024-07-29 20:25 ` |SUCCESS| " dpdklab
2024-07-29 20:28 ` |PENDING| " dpdklab
2024-07-29 20:28 ` dpdklab
2024-07-29 20:28 ` dpdklab
2024-07-29 20:34 ` dpdklab
2024-07-29 20:34 ` dpdklab
2024-07-29 20:34 ` dpdklab
2024-07-29 20:35 ` dpdklab
2024-07-29 20:45 ` dpdklab
2024-07-29 20:47 ` dpdklab
2024-07-29 20:49 ` dpdklab
2024-07-29 20:50 ` |SUCCESS| " dpdklab
2024-07-29 20:50 ` |PENDING| " dpdklab
2024-07-29 20:52 ` dpdklab
2024-07-29 20:53 ` dpdklab
2024-07-29 20:54 ` dpdklab
2024-07-29 20:54 ` dpdklab
2024-07-29 20:57 ` dpdklab
2024-07-29 20:58 ` dpdklab
2024-07-29 20:58 ` dpdklab
2024-07-29 20:58 ` dpdklab
2024-07-29 21:00 ` dpdklab
2024-07-29 21:00 ` dpdklab
2024-07-29 21:00 ` dpdklab
2024-07-29 21:01 ` dpdklab
2024-07-29 21:02 ` dpdklab
2024-07-29 21:02 ` dpdklab
2024-07-29 21:02 ` dpdklab
2024-07-29 21:05 ` dpdklab
2024-07-29 21:05 ` dpdklab
2024-07-29 21:08 ` dpdklab
2024-07-29 21:16 ` dpdklab
2024-07-29 21:19 ` dpdklab
2024-07-29 21:25 ` dpdklab
2024-07-29 21:28 ` dpdklab
2024-07-29 21:28 ` dpdklab
2024-07-29 21:29 ` dpdklab
2024-07-29 21:30 ` dpdklab
2024-07-29 21:32 ` |SUCCESS| " dpdklab
2024-07-29 21:32 ` |PENDING| " dpdklab
2024-07-29 21:33 ` dpdklab
2024-07-29 21:34 ` dpdklab
2024-07-29 21:36 ` dpdklab
2024-07-29 21:37 ` dpdklab
2024-07-29 21:39 ` dpdklab [this message]
2024-07-29 21:39 ` |SUCCESS| " dpdklab
2024-07-29 21:39 ` |PENDING| " dpdklab
2024-07-29 21:43 ` dpdklab
2024-07-29 21:44 ` dpdklab
2024-07-29 21:45 ` dpdklab
2024-07-29 21:46 ` dpdklab
2024-07-29 21:47 ` dpdklab
2024-07-29 21:49 ` dpdklab
2024-07-29 21:49 ` dpdklab
2024-07-29 21:49 ` dpdklab
2024-07-29 21:51 ` |SUCCESS| " dpdklab
2024-07-29 21:51 ` |PENDING| " dpdklab
2024-07-29 21:51 ` dpdklab
2024-07-29 21:53 ` dpdklab
2024-07-29 21:55 ` |SUCCESS| " dpdklab
2024-07-29 21:56 ` |PENDING| " dpdklab
2024-07-29 21:57 ` dpdklab
2024-07-29 21:59 ` |SUCCESS| " dpdklab
2024-07-29 21:59 ` |PENDING| " dpdklab
2024-07-29 22:00 ` |SUCCESS| " dpdklab
2024-07-29 22:00 ` dpdklab
2024-07-29 22:01 ` |PENDING| " dpdklab
2024-07-29 22:03 ` |SUCCESS| " dpdklab
2024-07-29 22:04 ` dpdklab
2024-07-29 22:13 ` |PENDING| " dpdklab
2024-07-29 22:13 ` dpdklab
2024-07-29 22:14 ` dpdklab
2024-07-29 22:14 ` dpdklab
2024-07-29 22:15 ` dpdklab
2024-07-29 22:17 ` dpdklab
2024-07-29 22:17 ` dpdklab
2024-07-29 22:19 ` dpdklab
2024-07-29 22:20 ` dpdklab
2024-07-29 22:22 ` |SUCCESS| " dpdklab
2024-07-29 22:22 ` dpdklab
2024-07-29 22:22 ` dpdklab
2024-07-29 22:22 ` |PENDING| " dpdklab
2024-07-29 22:23 ` dpdklab
2024-07-29 22:25 ` dpdklab
2024-07-29 22:27 ` dpdklab
2024-07-29 22:30 ` dpdklab
2024-07-29 22:31 ` dpdklab
2024-07-29 22:31 ` dpdklab
2024-07-29 22:34 ` dpdklab
2024-07-29 22:52 ` dpdklab
2024-07-30  1:26 ` |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=66a80bf9.050a0220.2ab814.a59fSMTPIN_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).