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| pw142452-142453 [PATCH] [2/2] net/nfp: fix AVX2 vector Rx
Date: Wed, 17 Jul 2024 00:26:28 -0700 (PDT)	[thread overview]
Message-ID: <66977224.050a0220.22c8f.49e6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240717032445.442348-3-chaoyong.he@corigine.com>

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

_Testing pending_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Wednesday, July 17 2024 03:24:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142452-142453 --> testing pending

Test environment and result as below:

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


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

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

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

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

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

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

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

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

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

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

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

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 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

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

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-17  7:26 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240717032445.442348-3-chaoyong.he@corigine.com>
2024-07-17  2:58 ` |SUCCESS| pw142452-142453 [PATCH 2/2] net/nfp: fix AVX2 vector Rx function memory overrun qemudev
2024-07-17  3:02 ` qemudev
2024-07-17  3:26 ` |SUCCESS| pw142453 " checkpatch
2024-07-17  4:23 ` 0-day Robot
2024-07-17  4:44 ` |SUCCESS| pw142452-142453 [PATCH] [2/2] net/nfp: fix AVX2 vector Rx dpdklab
2024-07-17  4:50 ` dpdklab
2024-07-17  4:52 ` dpdklab
2024-07-17  4:54 ` |PENDING| " dpdklab
2024-07-17  4:54 ` |SUCCESS| " dpdklab
2024-07-17  5:02 ` dpdklab
2024-07-17  5:05 ` dpdklab
2024-07-17  5:07 ` dpdklab
2024-07-17  5:07 ` dpdklab
2024-07-17  5:10 ` dpdklab
2024-07-17  5:13 ` dpdklab
2024-07-17  5:32 ` |PENDING| " dpdklab
2024-07-17  5:36 ` |SUCCESS| " dpdklab
2024-07-17  5:38 ` dpdklab
2024-07-17  5:39 ` |PENDING| " dpdklab
2024-07-17  5:40 ` dpdklab
2024-07-17  5:43 ` |SUCCESS| " dpdklab
2024-07-17  5:47 ` dpdklab
2024-07-17  5:52 ` |PENDING| " dpdklab
2024-07-17  5:52 ` |SUCCESS| " dpdklab
2024-07-17  5:54 ` |PENDING| " dpdklab
2024-07-17  5:58 ` dpdklab
2024-07-17  5:58 ` dpdklab
2024-07-17  6:00 ` dpdklab
2024-07-17  6:00 ` dpdklab
2024-07-17  6:00 ` dpdklab
2024-07-17  6:00 ` dpdklab
2024-07-17  6:03 ` dpdklab
2024-07-17  6:04 ` dpdklab
2024-07-17  6:04 ` dpdklab
2024-07-17  6:04 ` dpdklab
2024-07-17  6:04 ` dpdklab
2024-07-17  6:05 ` dpdklab
2024-07-17  6:05 ` dpdklab
2024-07-17  6:06 ` dpdklab
2024-07-17  6:06 ` dpdklab
2024-07-17  6:06 ` dpdklab
2024-07-17  6:07 ` dpdklab
2024-07-17  6:08 ` dpdklab
2024-07-17  6:08 ` dpdklab
2024-07-17  6:09 ` dpdklab
2024-07-17  6:09 ` dpdklab
2024-07-17  6:10 ` dpdklab
2024-07-17  6:11 ` dpdklab
2024-07-17  6:11 ` dpdklab
2024-07-17  6:11 ` |SUCCESS| " dpdklab
2024-07-17  6:12 ` |PENDING| " dpdklab
2024-07-17  6:12 ` dpdklab
2024-07-17  6:13 ` dpdklab
2024-07-17  6:16 ` dpdklab
2024-07-17  6:23 ` dpdklab
2024-07-17  6:23 ` dpdklab
2024-07-17  6:26 ` dpdklab
2024-07-17  6:26 ` dpdklab
2024-07-17  6:27 ` dpdklab
2024-07-17  6:28 ` dpdklab
2024-07-17  6:29 ` dpdklab
2024-07-17  6:29 ` dpdklab
2024-07-17  6:33 ` dpdklab
2024-07-17  6:34 ` dpdklab
2024-07-17  6:35 ` dpdklab
2024-07-17  6:36 ` dpdklab
2024-07-17  6:39 ` |SUCCESS| " dpdklab
2024-07-17  6:40 ` |PENDING| " dpdklab
2024-07-17  6:40 ` dpdklab
2024-07-17  6:42 ` dpdklab
2024-07-17  6:44 ` dpdklab
2024-07-17  6:48 ` dpdklab
2024-07-17  6:49 ` dpdklab
2024-07-17  6:50 ` dpdklab
2024-07-17  6:50 ` dpdklab
2024-07-17  6:50 ` dpdklab
2024-07-17  6:51 ` dpdklab
2024-07-17  6:52 ` dpdklab
2024-07-17  6:52 ` dpdklab
2024-07-17  6:52 ` dpdklab
2024-07-17  6:53 ` dpdklab
2024-07-17  6:56 ` dpdklab
2024-07-17  6:57 ` dpdklab
2024-07-17  6:58 ` dpdklab
2024-07-17  7:00 ` dpdklab
2024-07-17  7:01 ` dpdklab
2024-07-17  7:01 ` dpdklab
2024-07-17  7:02 ` dpdklab
2024-07-17  7:03 ` dpdklab
2024-07-17  7:07 ` dpdklab
2024-07-17  7:08 ` dpdklab
2024-07-17  7:12 ` dpdklab
2024-07-17  7:16 ` dpdklab
2024-07-17  7:21 ` dpdklab
2024-07-17  7:26 ` dpdklab [this message]
2024-07-17  7:28 ` |SUCCESS| " dpdklab
2024-07-17  7:28 ` dpdklab
2024-07-17  7:35 ` |PENDING| " dpdklab
2024-07-17  7:35 ` dpdklab
2024-07-17  7:38 ` |SUCCESS| " dpdklab
2024-07-17  7:45 ` |PENDING| " dpdklab
2024-07-17  7:47 ` |SUCCESS| " dpdklab
2024-07-17  7:47 ` dpdklab
2024-07-17  7:47 ` |PENDING| " dpdklab
2024-07-17  7:49 ` dpdklab
2024-07-17  7:59 ` dpdklab
2024-07-17  8:00 ` dpdklab
2024-07-17  8:04 ` dpdklab
2024-07-17  8:05 ` dpdklab
2024-07-17  8:08 ` dpdklab
2024-07-17  8:09 ` dpdklab
2024-07-17  8:11 ` dpdklab
2024-07-17  8:15 ` dpdklab
2024-07-17  8:16 ` dpdklab
2024-07-17  8:25 ` |SUCCESS| " dpdklab
2024-07-17  8:27 ` 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=66977224.050a0220.22c8f.49e6SMTPIN_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).