automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: |SUCCESS| pw104680 [PATCH] examples/ipsec-secgw: set L4 length for TSO packets
Date: Wed, 24 Nov 2021 16:12:09 -0500 (EST)	[thread overview]
Message-ID: <20211124211209.7EDAC60524@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 4287 bytes --]

Test-Label: iol-x86_64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/104680

_Testing PASS_

Submitter: Radu Nicolau <radu.nicolau@intel.com>
Date: Wednesday, November 24 2021 17:33:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0c6e27549c03695f85d949f5195a166b449b419c

104680 --> testing pass

Test environment and result as below:

+---------------------+----------------------+--------------------+
|     Environment     | dpdk_mingw64_compile | dpdk_meson_compile |
+=====================+======================+====================+
| Windows Server 2019 | PASS                 | PASS               |
+---------------------+----------------------+--------------------+
| FreeBSD 13          | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| openSUSE Leap 15    | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Ubuntu 18.04        | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| CentOS 8            | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Fedora 32           | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Fedora 31           | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Ubuntu 20.04        | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| RHEL 7              | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| RHEL8               | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Arch Linux          | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Fedora 33           | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Fedora 34           | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Alpine              | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| CentOS Stream 8     | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+
| Fedora 34 clang     | SKIPPED              | PASS               |
+---------------------+----------------------+--------------------+


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

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

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

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

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

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

Fedora 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

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

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

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-11-24 21:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 21:12 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-24 21:02 dpdklab
2021-11-24 20:58 dpdklab
2021-11-24 20:51 dpdklab
2021-11-24 20:41 dpdklab
2021-11-24 20:40 dpdklab
2021-11-24 20:33 dpdklab
2021-11-24 20:32 dpdklab
2021-11-24 20:31 dpdklab
2021-11-24 20:24 dpdklab
2021-11-24 20:21 dpdklab
2021-11-24 20:20 dpdklab
     [not found] <20211124173352.502609-1-radu.nicolau@intel.com>
2021-11-24 17:52 ` checkpatch
2021-11-24 18:18 ` 0-day Robot

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=20211124211209.7EDAC60524@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@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).