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| pw135884 [PATCH] maintainers: update for e1000/igc
Date: Tue, 16 Jan 2024 17:33:52 -0800 (PST)	[thread overview]
Message-ID: <65a72e80.050a0220.21b9c.e373SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Simei Su <simei.su@intel.com>
Date: Tuesday, January 16 2024 07:54:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a

135884 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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

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

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

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

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

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

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

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

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-17  1:33 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17  1:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-17 18:18 dpdklab
     [not found] <20240116075418.181911-1-simei.su@intel.com>
2024-01-16  8:10 ` checkpatch
2024-01-16  8:57 ` 0-day Robot
2024-01-17  3:05 ` qemudev
2024-01-17  3:10 ` qemudev
2024-01-17  2:49 dpdklab
2024-01-17  2:32 dpdklab
2024-01-17  2:25 dpdklab
2024-01-17  2:22 dpdklab
2024-01-17  2:22 dpdklab
2024-01-17  2:21 dpdklab
2024-01-17  2:18 dpdklab
2024-01-17  2:17 dpdklab
2024-01-17  2:16 dpdklab
2024-01-17  2:14 dpdklab
2024-01-17  2:12 dpdklab
2024-01-17  2:11 dpdklab
2024-01-17  2:11 dpdklab
2024-01-17  1:58 dpdklab
2024-01-17  1:58 dpdklab
2024-01-17  1:57 dpdklab
2024-01-17  1:57 dpdklab
2024-01-17  1:38 dpdklab
2024-01-17  1:38 dpdklab
2024-01-17  1:38 dpdklab
2024-01-17  1:37 dpdklab
2024-01-17  1:37 dpdklab
2024-01-17  1:36 dpdklab
2024-01-17  1:36 dpdklab
2024-01-17  1:35 dpdklab
2024-01-17  1:34 dpdklab
2024-01-17  1:34 dpdklab
2024-01-17  1:33 dpdklab
2024-01-17  1:33 dpdklab
2024-01-17  1:33 dpdklab
2024-01-17  1:32 dpdklab
2024-01-17  1:32 dpdklab
2024-01-17  1:32 dpdklab
2024-01-17  1:28 dpdklab
2024-01-17  1:27 dpdklab
2024-01-17  1:26 dpdklab
2024-01-17  1:25 dpdklab
2024-01-17  1:24 dpdklab
2024-01-17  1:23 dpdklab
2024-01-17  1:22 dpdklab
2024-01-17  1:19 dpdklab
2024-01-17  1:06 dpdklab
2024-01-17  0:47 dpdklab
2024-01-17  0:46 dpdklab
2024-01-16 23:26 dpdklab
2024-01-16 23:22 dpdklab
2024-01-16 23:17 dpdklab
2024-01-16 23:17 dpdklab
2024-01-16 23:14 dpdklab
2024-01-16 22:58 dpdklab
2024-01-16 22:58 dpdklab
2024-01-16 22:57 dpdklab
2024-01-16 22:56 dpdklab
2024-01-16 22:56 dpdklab
2024-01-16 22:54 dpdklab
2024-01-16 22:52 dpdklab
2024-01-16 22:51 dpdklab
2024-01-16 22:50 dpdklab
2024-01-16 22:41 dpdklab
2024-01-16 22:33 dpdklab
2024-01-16 22:32 dpdklab
2024-01-16 22:12 dpdklab
2024-01-16 22:11 dpdklab
2024-01-16 22:09 dpdklab
2024-01-16 22:06 dpdklab
2024-01-16 22:04 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=65a72e80.050a0220.21b9c.e373SMTPIN_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).