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| pw135771 [PATCH] [v10] gro: fix reordering of packets in G
Date: Sun, 07 Jan 2024 04:06:36 -0800 (PST)	[thread overview]
Message-ID: <659a93cc.170a0220.e013e.80a2SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Date: Sunday, January 07 2024 11:21:48 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

135771 --> testing pass

Test environment and result as below:

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


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

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

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-07 12:06 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 12:06 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-07 14:52 dpdklab
2024-01-07 12:55 dpdklab
2024-01-07 12:39 dpdklab
2024-01-07 12:35 dpdklab
2024-01-07 12:27 dpdklab
2024-01-07 12:26 dpdklab
2024-01-07 12:26 dpdklab
2024-01-07 12:26 dpdklab
2024-01-07 12:26 dpdklab
2024-01-07 12:25 dpdklab
2024-01-07 12:24 dpdklab
2024-01-07 12:23 dpdklab
2024-01-07 12:22 dpdklab
2024-01-07 12:20 dpdklab
2024-01-07 12:20 dpdklab
2024-01-07 12:19 dpdklab
2024-01-07 12:19 dpdklab
2024-01-07 12:17 dpdklab
2024-01-07 12:17 dpdklab
2024-01-07 12:15 dpdklab
2024-01-07 12:15 dpdklab
2024-01-07 12:14 dpdklab
2024-01-07 12:14 dpdklab
2024-01-07 12:14 dpdklab
2024-01-07 12:14 dpdklab
2024-01-07 12:14 dpdklab
2024-01-07 12:13 dpdklab
2024-01-07 12:13 dpdklab
2024-01-07 12:13 dpdklab
2024-01-07 12:13 dpdklab
2024-01-07 12:13 dpdklab
2024-01-07 12:13 dpdklab
2024-01-07 12:12 dpdklab
2024-01-07 12:12 dpdklab
2024-01-07 12:12 dpdklab
2024-01-07 12:11 dpdklab
2024-01-07 12:11 dpdklab
2024-01-07 12:11 dpdklab
2024-01-07 12:11 dpdklab
2024-01-07 12:11 dpdklab
2024-01-07 12:10 dpdklab
2024-01-07 12:10 dpdklab
2024-01-07 12:10 dpdklab
2024-01-07 12:10 dpdklab
2024-01-07 12:10 dpdklab
2024-01-07 12:09 dpdklab
2024-01-07 12:09 dpdklab
2024-01-07 12:09 dpdklab
2024-01-07 12:09 dpdklab
2024-01-07 12:09 dpdklab
2024-01-07 12:08 dpdklab
2024-01-07 12:08 dpdklab
2024-01-07 12:08 dpdklab
2024-01-07 12:08 dpdklab
2024-01-07 12:07 dpdklab
2024-01-07 12:07 dpdklab
2024-01-07 12:07 dpdklab
2024-01-07 12:07 dpdklab
2024-01-07 12:06 dpdklab
2024-01-07 12:06 dpdklab
2024-01-07 12:06 dpdklab
2024-01-07 12:05 dpdklab
2024-01-07 12:05 dpdklab
2024-01-07 12:05 dpdklab
2024-01-07 12: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=659a93cc.170a0220.e013e.80a2SMTPIN_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).