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| pw136249-136250 [PATCH] [2/2] net/ngbe: add vectorized fun
Date: Wed, 31 Jan 2024 21:30:32 -0800 (PST)	[thread overview]
Message-ID: <65bb2c78.810a0220.512a3.c92eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136250

_Testing PASS_

Submitter: Jiawen Wu <jiawenwu@trustnetic.com>
Date: Thursday, February 01 2024 03:00:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca

136249-136250 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Alpine              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

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

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

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

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

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/29009/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-01  5:30 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  5:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-01  6:44 dpdklab
2024-02-01  6:42 dpdklab
2024-02-01  6:23 dpdklab
2024-02-01  6:19 dpdklab
2024-02-01  6:14 dpdklab
2024-02-01  5:52 dpdklab
2024-02-01  5:51 dpdklab
2024-02-01  5:50 dpdklab
2024-02-01  5:50 dpdklab
2024-02-01  5:49 dpdklab
2024-02-01  5:43 dpdklab
2024-02-01  5:37 dpdklab
2024-02-01  5:37 dpdklab
2024-02-01  5:37 dpdklab
2024-02-01  5:37 dpdklab
2024-02-01  5:37 dpdklab
2024-02-01  5:37 dpdklab
2024-02-01  5:36 dpdklab
2024-02-01  5:36 dpdklab
2024-02-01  5:36 dpdklab
2024-02-01  5:35 dpdklab
2024-02-01  5:35 dpdklab
2024-02-01  5:31 dpdklab
2024-02-01  5:31 dpdklab
2024-02-01  5:30 dpdklab
2024-02-01  5:29 dpdklab
2024-02-01  5:25 dpdklab
2024-02-01  5:24 dpdklab
2024-02-01  5:23 dpdklab
2024-02-01  5:22 dpdklab
2024-02-01  5:21 dpdklab
2024-02-01  5:21 dpdklab
2024-02-01  5:20 dpdklab
2024-02-01  5:20 dpdklab
2024-02-01  5:20 dpdklab
2024-02-01  5:20 dpdklab
2024-02-01  5:19 dpdklab
2024-02-01  5:19 dpdklab
2024-02-01  5:19 dpdklab
2024-02-01  5:19 dpdklab
2024-02-01  5:17 dpdklab
2024-02-01  5:16 dpdklab
2024-02-01  5:16 dpdklab
2024-02-01  5:16 dpdklab
2024-02-01  5:16 dpdklab
2024-02-01  5:15 dpdklab
2024-02-01  5:15 dpdklab
2024-02-01  5:03 dpdklab
2024-02-01  5:02 dpdklab
2024-02-01  5:01 dpdklab
2024-02-01  5:01 dpdklab
2024-02-01  5:00 dpdklab
2024-02-01  4:58 dpdklab
2024-02-01  4:58 dpdklab
2024-02-01  4:58 dpdklab
2024-02-01  4:57 dpdklab
2024-02-01  4:57 dpdklab
2024-02-01  4:57 dpdklab
2024-02-01  4:57 dpdklab
2024-02-01  4:56 dpdklab
2024-02-01  4:55 dpdklab
2024-02-01  4:54 dpdklab
2024-02-01  4:53 dpdklab
2024-02-01  4:52 dpdklab
2024-02-01  4:52 dpdklab
2024-02-01  4:51 dpdklab
2024-02-01  4:51 dpdklab
2024-02-01  4:49 dpdklab
2024-02-01  4:41 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=65bb2c78.810a0220.512a3.c92eSMTPIN_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).