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| pw140746 [PATCH] [v1,1/1] crypto/ipsec_mb: unify some IPse
Date: Wed, 05 Jun 2024 05:43:22 -0700 (PDT)	[thread overview]
Message-ID: <66605d6a.170a0220.11e311.7012SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240605085346.272837-2-brian.dooley@intel.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140746

_Testing PASS_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Wednesday, June 05 2024 08:53:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:367b8db312517edb9f5340d280e77b1437d84dd3

140746 --> testing pass

Test environment and result as below:

+-----------------------------+----------------+--------------+
|         Environment         | dpdk_unit_test | lpm_autotest |
+=============================+================+==============+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Debian 12 (arm)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM)    | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Fedora 38 (ARM)             | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | PASS         |
+-----------------------------+----------------+--------------+


32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-05 12:43 UTC|newest]

Thread overview: 96+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240605085346.272837-2-brian.dooley@intel.com>
2024-06-05  8:34 ` |SUCCESS| pw140746 [PATCH v1 1/1] crypto/ipsec_mb: unify some IPsec MB PMDs qemudev
2024-06-05  8:39 ` qemudev
2024-06-05  8:54 ` checkpatch
2024-06-05  9:55 ` |FAILURE| " 0-day Robot
2024-06-05 10:09 ` |SUCCESS| pw140746 [PATCH] [v1,1/1] crypto/ipsec_mb: unify some IPse dpdklab
2024-06-05 10:17 ` dpdklab
2024-06-05 10:18 ` dpdklab
2024-06-05 10:18 ` dpdklab
2024-06-05 10:19 ` dpdklab
2024-06-05 10:22 ` dpdklab
2024-06-05 10:31 ` dpdklab
2024-06-05 10:31 ` dpdklab
2024-06-05 10:34 ` dpdklab
2024-06-05 10:35 ` dpdklab
2024-06-05 10:35 ` dpdklab
2024-06-05 10:44 ` dpdklab
2024-06-05 10:44 ` dpdklab
2024-06-05 10:47 ` dpdklab
2024-06-05 11:16 ` dpdklab
2024-06-05 11:18 ` dpdklab
2024-06-05 11:19 ` dpdklab
2024-06-05 11:21 ` dpdklab
2024-06-05 11:28 ` dpdklab
2024-06-05 11:30 ` dpdklab
2024-06-05 11:33 ` dpdklab
2024-06-05 11:33 ` dpdklab
2024-06-05 11:37 ` dpdklab
2024-06-05 11:38 ` dpdklab
2024-06-05 11:38 ` dpdklab
2024-06-05 11:38 ` dpdklab
2024-06-05 11:38 ` dpdklab
2024-06-05 11:39 ` dpdklab
2024-06-05 11:39 ` dpdklab
2024-06-05 11:40 ` dpdklab
2024-06-05 11:41 ` dpdklab
2024-06-05 11:52 ` dpdklab
2024-06-05 11:56 ` dpdklab
2024-06-05 11:57 ` dpdklab
2024-06-05 11:58 ` dpdklab
2024-06-05 12:00 ` dpdklab
2024-06-05 12:07 ` dpdklab
2024-06-05 12:11 ` dpdklab
2024-06-05 12:19 ` dpdklab
2024-06-05 12:21 ` dpdklab
2024-06-05 12:23 ` dpdklab
2024-06-05 12:23 ` dpdklab
2024-06-05 12:24 ` dpdklab
2024-06-05 12:27 ` dpdklab
2024-06-05 12:30 ` dpdklab
2024-06-05 12:31 ` dpdklab
2024-06-05 12:35 ` dpdklab
2024-06-05 12:35 ` dpdklab
2024-06-05 12:36 ` dpdklab
2024-06-05 12:37 ` dpdklab
2024-06-05 12:38 ` dpdklab
2024-06-05 12:41 ` dpdklab
2024-06-05 12:42 ` dpdklab
2024-06-05 12:43 ` dpdklab [this message]
2024-06-05 12:43 ` dpdklab
2024-06-05 12:45 ` dpdklab
2024-06-05 12:46 ` dpdklab
2024-06-05 12:46 ` dpdklab
2024-06-05 12:56 ` dpdklab
2024-06-05 12:59 ` dpdklab
2024-06-05 12:59 ` dpdklab
2024-06-05 13:00 ` dpdklab
2024-06-05 13:00 ` dpdklab
2024-06-05 13:00 ` dpdklab
2024-06-05 13:00 ` dpdklab
2024-06-05 13:01 ` dpdklab
2024-06-05 13:01 ` dpdklab
2024-06-05 13:02 ` dpdklab
2024-06-05 13:08 ` dpdklab
2024-06-05 13:18 ` |WARNING| " dpdklab
2024-06-05 13:18 ` dpdklab
2024-06-05 13:18 ` |SUCCESS| " dpdklab
2024-06-05 13:19 ` |WARNING| " dpdklab
2024-06-05 13:19 ` dpdklab
2024-06-05 13:19 ` dpdklab
2024-06-05 13:20 ` dpdklab
2024-06-05 13:20 ` dpdklab
2024-06-05 13:21 ` |SUCCESS| " dpdklab
2024-06-05 13:21 ` |WARNING| " dpdklab
2024-06-05 13:22 ` |SUCCESS| " dpdklab
2024-06-05 13:23 ` dpdklab
2024-06-05 13:23 ` dpdklab
2024-06-05 13:26 ` dpdklab
2024-06-05 13:27 ` dpdklab
2024-06-05 13:27 ` |WARNING| " dpdklab
2024-06-05 13:29 ` |SUCCESS| " dpdklab
2024-06-05 13:58 ` dpdklab
2024-06-05 18:12 ` dpdklab
2024-06-05 20:38 ` dpdklab
2024-06-05 22:59 ` dpdklab
2024-06-05 23:06 ` dpdklab
2024-06-05 23:30 ` 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=66605d6a.170a0220.11e311.7012SMTPIN_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).