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| pw137960 [PATCH] [v2] hash: make GFNI stubs inline (again)
Date: Tue, 05 Mar 2024 00:09:55 -0800 (PST)	[thread overview]
Message-ID: <65e6d353.170a0220.5511d.ea30SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240305030819.276707-1-stephen@networkplumber.org>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137960

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, March 05 2024 03:07:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:be793709e7b044cd4f806d6103bf3c046311a3c7

137960 --> functional testing pass

Test environment and result as below:

Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

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-05  8:09 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240305030819.276707-1-stephen@networkplumber.org>
2024-03-05  2:45 ` |SUCCESS| pw137960 [PATCH v2] " qemudev
2024-03-05  2:49 ` qemudev
2024-03-05  3:09 ` |WARNING| pw137960 [PATCH v2] hash: make GFNI stubs inline again checkpatch
2024-03-05  4:05 ` |SUCCESS| pw137960 [PATCH v2] hash: make GFNI stubs inline (again) 0-day Robot
2024-03-05  8:08 ` |SUCCESS| pw137960 [PATCH] [v2] " dpdklab
2024-03-05  8:08 ` dpdklab
2024-03-05  8:08 ` dpdklab
2024-03-05  8:09 ` dpdklab
2024-03-05  8:09 ` dpdklab
2024-03-05  8:09 ` dpdklab [this message]
2024-03-05  8:10 ` dpdklab
2024-03-05  8:10 ` dpdklab
2024-03-05  8:11 ` dpdklab
2024-03-05  8:11 ` dpdklab
2024-03-05  8:11 ` dpdklab
2024-03-05  8:12 ` dpdklab
2024-03-05  8:12 ` dpdklab
2024-03-05  8:12 ` dpdklab
2024-03-05  8:13 ` dpdklab
2024-03-05  8:14 ` dpdklab
2024-03-05  8:15 ` dpdklab
2024-03-05  8:15 ` dpdklab
2024-03-05  8:15 ` dpdklab
2024-03-05  8:16 ` dpdklab
2024-03-05  8:17 ` dpdklab
2024-03-05  8:19 ` dpdklab
2024-03-05  8:19 ` dpdklab
2024-03-05  8:20 ` dpdklab
2024-03-05  8:20 ` dpdklab
2024-03-05  8:21 ` dpdklab
2024-03-05  8:21 ` dpdklab
2024-03-05  8:21 ` dpdklab
2024-03-05  8:22 ` dpdklab
2024-03-05  8:23 ` dpdklab
2024-03-05  8:23 ` dpdklab
2024-03-05  8:23 ` dpdklab
2024-03-05  8:23 ` dpdklab
2024-03-05  8:23 ` dpdklab
2024-03-05  8:24 ` dpdklab
2024-03-05  8:25 ` dpdklab
2024-03-05  8:26 ` dpdklab
2024-03-05  8:26 ` dpdklab
2024-03-05  8:26 ` dpdklab
2024-03-05  8:27 ` dpdklab
2024-03-05  8:28 ` dpdklab
2024-03-05  8:28 ` dpdklab
2024-03-05  8:31 ` dpdklab
2024-03-05  8:31 ` dpdklab
2024-03-05  8:31 ` dpdklab
2024-03-05  8:31 ` dpdklab
2024-03-05  8:32 ` dpdklab
2024-03-05  8:32 ` dpdklab
2024-03-05  8:33 ` dpdklab
2024-03-05  8:34 ` dpdklab
2024-03-05  8:35 ` dpdklab
2024-03-05  8:35 ` dpdklab
2024-03-05  8:36 ` dpdklab
2024-03-05  8:37 ` dpdklab
2024-03-05  8:40 ` dpdklab
2024-03-05  8:41 ` dpdklab
2024-03-05  8:45 ` dpdklab
2024-03-05  8:46 ` dpdklab
2024-03-05  8:47 ` dpdklab
2024-03-05  8:48 ` dpdklab
2024-03-05  8:51 ` dpdklab
2024-03-05  8:51 ` dpdklab
2024-03-05  8:51 ` dpdklab
2024-03-05  8:51 ` dpdklab
2024-03-05  8:54 ` dpdklab
2024-03-05  8:55 ` dpdklab
2024-03-05  9:32 ` dpdklab
2024-03-05  9:56 ` dpdklab
2024-03-08 20:19 ` dpdklab
2024-03-08 20:51 ` dpdklab
2024-03-08 21:55 ` 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=65e6d353.170a0220.5511d.ea30SMTPIN_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).