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| pw138856 [PATCH] doc: clarify ipsec-secgw documentation on
Date: Wed, 27 Mar 2024 04:36:08 -0700 (PDT)	[thread overview]
Message-ID: <660404a8.020a0220.c96f2.7cd0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240327105113.3116549-1-vladimir.medvedkin@intel.com>

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

_Testing PASS_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Wednesday, March 27 2024 10:51:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ded4d4765171b88470e59307f10625e942f22fca

138856 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| FreeBSD 13.2        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Debian Bullseye     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PASS                 | PASS              |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 9     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Debian 11 (arm)     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 37           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+


FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 14.0.5

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

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 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-27 11:36 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240327105113.3116549-1-vladimir.medvedkin@intel.com>
2024-03-27 10:29 ` |SUCCESS| pw138856 [PATCH] doc: clarify ipsec-secgw documentation on TSO qemudev
2024-03-27 10:33 ` qemudev
2024-03-27 10:53 ` checkpatch
2024-03-27 11:35 ` |SUCCESS| pw138856 [PATCH] doc: clarify ipsec-secgw documentation on dpdklab
2024-03-27 11:35 ` dpdklab
2024-03-27 11:36 ` dpdklab [this message]
2024-03-27 11:36 ` dpdklab
2024-03-27 11:36 ` dpdklab
2024-03-27 11:36 ` dpdklab
2024-03-27 11:36 ` dpdklab
2024-03-27 11:37 ` dpdklab
2024-03-27 11:37 ` dpdklab
2024-03-27 11:37 ` dpdklab
2024-03-27 11:37 ` dpdklab
2024-03-27 11:37 ` dpdklab
2024-03-27 11:38 ` dpdklab
2024-03-27 11:38 ` dpdklab
2024-03-27 11:38 ` dpdklab
2024-03-27 11:38 ` dpdklab
2024-03-27 11:39 ` dpdklab
2024-03-27 11:39 ` dpdklab
2024-03-27 11:39 ` dpdklab
2024-03-27 11:39 ` dpdklab
2024-03-27 11:39 ` dpdklab
2024-03-27 11:39 ` dpdklab
2024-03-27 11:39 ` dpdklab
2024-03-27 11:40 ` dpdklab
2024-03-27 11:40 ` dpdklab
2024-03-27 11:40 ` dpdklab
2024-03-27 11:40 ` dpdklab
2024-03-27 11:40 ` dpdklab
2024-03-27 11:40 ` dpdklab
2024-03-27 11:42 ` dpdklab
2024-03-27 11:42 ` dpdklab
2024-03-27 11:42 ` dpdklab
2024-03-27 11:43 ` dpdklab
2024-03-27 11:43 ` dpdklab
2024-03-27 11:44 ` dpdklab
2024-03-27 11:44 ` dpdklab
2024-03-27 11:45 ` |SUCCESS| pw138856 [PATCH] doc: clarify ipsec-secgw documentation on TSO 0-day Robot
2024-03-27 11:45 ` |SUCCESS| pw138856 [PATCH] doc: clarify ipsec-secgw documentation on dpdklab
2024-03-27 11:45 ` dpdklab
2024-03-27 11:46 ` dpdklab
2024-03-27 11:47 ` dpdklab
2024-03-27 11:48 ` dpdklab
2024-03-27 11:49 ` dpdklab
2024-03-27 11:49 ` dpdklab
2024-03-27 11:49 ` dpdklab
2024-03-27 11:50 ` dpdklab
2024-03-27 11:51 ` dpdklab
2024-03-27 11:52 ` dpdklab
2024-03-27 11:54 ` dpdklab
2024-03-27 11:54 ` dpdklab
2024-03-27 11:56 ` dpdklab
2024-03-27 11:59 ` dpdklab
2024-03-27 12:02 ` dpdklab
2024-03-27 12:02 ` dpdklab
2024-03-27 12:02 ` dpdklab
2024-03-27 12:03 ` dpdklab
2024-03-27 12:03 ` dpdklab
2024-03-27 12:03 ` dpdklab
2024-03-27 12:03 ` dpdklab
2024-03-27 12:03 ` dpdklab
2024-03-27 12:03 ` dpdklab
2024-03-27 12:04 ` dpdklab
2024-03-27 12:04 ` dpdklab
2024-03-27 12:05 ` dpdklab
2024-03-27 12:05 ` dpdklab
2024-03-27 12:10 ` dpdklab
2024-03-27 12:11 ` dpdklab
2024-03-27 12:16 ` dpdklab
2024-03-27 12:20 ` dpdklab
2024-03-27 12:21 ` dpdklab
2024-03-27 12:22 ` dpdklab
2024-03-27 12:30 ` dpdklab
2024-03-27 12:33 ` dpdklab
2024-03-27 12:33 ` dpdklab
2024-03-27 12:35 ` dpdklab
2024-03-27 12:36 ` dpdklab
2024-03-27 12:37 ` dpdklab
2024-03-27 12:49 ` dpdklab
2024-03-27 12:56 ` dpdklab
2024-03-27 12:59 ` dpdklab
2024-03-27 14:05 ` dpdklab
2024-03-27 14:41 ` dpdklab
2024-04-02  8:11 ` dpdklab
2024-04-02  8:15 ` dpdklab
2024-04-02  8:20 ` dpdklab
2024-04-02  8:23 ` dpdklab
2024-04-02  8:43 ` 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=660404a8.020a0220.c96f2.7cd0SMTPIN_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).