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| pw138337 [PATCH] [v2] examples/ipsec-secgw: fix SA salt en
Date: Wed, 13 Mar 2024 20:07:25 -0700 (PDT)	[thread overview]
Message-ID: <65f269ed.b00a0220.e6e0f.210eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314020052.3107549-1-chaoyong.he@corigine.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138337

_Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, March 14 2024 02:00:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3

138337 --> testing pass

Test environment and result as below:

+-----------------+----------------+
|   Environment   | dpdk_unit_test |
+=================+================+
| Fedora 38       | PASS           |
+-----------------+----------------+
| CentOS Stream 9 | PASS           |
+-----------------+----------------+
| CentOS Stream 8 | PASS           |
+-----------------+----------------+
| Fedora 37       | PASS           |
+-----------------+----------------+


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

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

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

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

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-14  3:07 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240314020052.3107549-1-chaoyong.he@corigine.com>
2024-03-14  1:39 ` |SUCCESS| pw138337 [PATCH v2] examples/ipsec-secgw: fix SA salt endianness problem qemudev
2024-03-14  1:43 ` qemudev
2024-03-14  2:02 ` checkpatch
2024-03-14  2:48 ` |SUCCESS| pw138337 [PATCH] [v2] examples/ipsec-secgw: fix SA salt en dpdklab
2024-03-14  2:53 ` dpdklab
2024-03-14  2:54 ` dpdklab
2024-03-14  2:54 ` dpdklab
2024-03-14  2:54 ` dpdklab
2024-03-14  2:54 ` dpdklab
2024-03-14  2:55 ` dpdklab
2024-03-14  2:56 ` dpdklab
2024-03-14  2:56 ` dpdklab
2024-03-14  2:57 ` dpdklab
2024-03-14  2:57 ` dpdklab
2024-03-14  2:57 ` dpdklab
2024-03-14  2:57 ` dpdklab
2024-03-14  2:58 ` dpdklab
2024-03-14  2:58 ` dpdklab
2024-03-14  2:58 ` dpdklab
2024-03-14  2:59 ` dpdklab
2024-03-14  3:00 ` dpdklab
2024-03-14  3:00 ` dpdklab
2024-03-14  3:00 ` dpdklab
2024-03-14  3:01 ` dpdklab
2024-03-14  3:01 ` dpdklab
2024-03-14  3:01 ` dpdklab
2024-03-14  3:01 ` dpdklab
2024-03-14  3:01 ` dpdklab
2024-03-14  3:02 ` dpdklab
2024-03-14  3:02 ` dpdklab
2024-03-14  3:02 ` dpdklab
2024-03-14  3:02 ` dpdklab
2024-03-14  3:02 ` dpdklab
2024-03-14  3:03 ` dpdklab
2024-03-14  3:03 ` |SUCCESS| pw138337 [PATCH v2] examples/ipsec-secgw: fix SA salt endianness problem 0-day Robot
2024-03-14  3:03 ` |SUCCESS| pw138337 [PATCH] [v2] examples/ipsec-secgw: fix SA salt en dpdklab
2024-03-14  3:03 ` dpdklab
2024-03-14  3:03 ` dpdklab
2024-03-14  3:03 ` dpdklab
2024-03-14  3:04 ` dpdklab
2024-03-14  3:04 ` dpdklab
2024-03-14  3:04 ` dpdklab
2024-03-14  3:04 ` dpdklab
2024-03-14  3:05 ` dpdklab
2024-03-14  3:05 ` dpdklab
2024-03-14  3:05 ` dpdklab
2024-03-14  3:05 ` dpdklab
2024-03-14  3:05 ` dpdklab
2024-03-14  3:05 ` dpdklab
2024-03-14  3:06 ` dpdklab
2024-03-14  3:06 ` dpdklab
2024-03-14  3:07 ` dpdklab [this message]
2024-03-14  3:08 ` dpdklab
2024-03-14  3:09 ` dpdklab
2024-03-14  3:09 ` dpdklab
2024-03-14  3:09 ` dpdklab
2024-03-14  3:10 ` dpdklab
2024-03-14  3:10 ` dpdklab
2024-03-14  3:10 ` dpdklab
2024-03-14  3:11 ` dpdklab
2024-03-14  3:11 ` dpdklab
2024-03-14  3:11 ` dpdklab
2024-03-14  3:12 ` dpdklab
2024-03-14  3:13 ` dpdklab
2024-03-14  3:14 ` dpdklab
2024-03-14  3:15 ` dpdklab
2024-03-14  3:16 ` dpdklab
2024-03-14  3:17 ` dpdklab
2024-03-14  3:21 ` dpdklab
2024-03-14  3:24 ` dpdklab
2024-03-14  3:24 ` dpdklab
2024-03-14  3:24 ` dpdklab
2024-03-14  3:24 ` dpdklab
2024-03-14  3:31 ` dpdklab
2024-03-14  3:53 ` dpdklab
2024-03-14  4:44 ` dpdklab
2024-03-17 16:17 ` dpdklab
2024-03-17 16:39 ` 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=65f269ed.b00a0220.e6e0f.210eSMTPIN_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).