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| pw140237 [PATCH] [v2] hash: provide crc32 functions based
Date: Tue, 21 May 2024 18:21:16 -0700 (PDT)	[thread overview]
Message-ID: <664d488c.050a0220.ee9a8.de00SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1716336134-27366-2-git-send-email-roretzla@linux.microsoft.com>

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

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, May 22 2024 00:02:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33

140237 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-22  1:21 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1716336134-27366-2-git-send-email-roretzla@linux.microsoft.com>
2024-05-21 23:36 ` |SUCCESS| pw140237 [PATCH v2] hash: provide crc32 functions based on intrinsics qemudev
2024-05-21 23:40 ` qemudev
2024-05-22  0:03 ` checkpatch
2024-05-22  1:04 ` 0-day Robot
2024-05-22  1:12 ` |SUCCESS| pw140237 [PATCH] [v2] hash: provide crc32 functions based dpdklab
2024-05-22  1:12 ` dpdklab
2024-05-22  1:13 ` dpdklab
2024-05-22  1:13 ` dpdklab
2024-05-22  1:14 ` dpdklab
2024-05-22  1:14 ` dpdklab
2024-05-22  1:14 ` dpdklab
2024-05-22  1:15 ` dpdklab
2024-05-22  1:15 ` dpdklab
2024-05-22  1:15 ` dpdklab
2024-05-22  1:16 ` dpdklab
2024-05-22  1:18 ` dpdklab
2024-05-22  1:18 ` dpdklab
2024-05-22  1:18 ` dpdklab
2024-05-22  1:19 ` dpdklab
2024-05-22  1:19 ` dpdklab
2024-05-22  1:19 ` dpdklab
2024-05-22  1:19 ` dpdklab
2024-05-22  1:20 ` dpdklab
2024-05-22  1:20 ` dpdklab
2024-05-22  1:20 ` dpdklab
2024-05-22  1:20 ` dpdklab
2024-05-22  1:20 ` dpdklab
2024-05-22  1:21 ` dpdklab
2024-05-22  1:21 ` dpdklab [this message]
2024-05-22  1:21 ` dpdklab
2024-05-22  1:22 ` dpdklab
2024-05-22  1:22 ` dpdklab
2024-05-22  1:22 ` dpdklab
2024-05-22  1:22 ` dpdklab
2024-05-22  1:22 ` dpdklab
2024-05-22  1:22 ` dpdklab
2024-05-22  1:22 ` dpdklab
2024-05-22  1:22 ` dpdklab
2024-05-22  1:23 ` dpdklab
2024-05-22  1:23 ` dpdklab
2024-05-22  1:24 ` dpdklab
2024-05-22  1:24 ` dpdklab
2024-05-22  1:24 ` dpdklab
2024-05-22  1:24 ` dpdklab
2024-05-22  1:24 ` dpdklab
2024-05-22  1:24 ` dpdklab
2024-05-22  1:25 ` dpdklab
2024-05-22  1:25 ` dpdklab
2024-05-22  1:25 ` dpdklab
2024-05-22  1:25 ` dpdklab
2024-05-22  1:25 ` dpdklab
2024-05-22  1:25 ` dpdklab
2024-05-22  1:25 ` dpdklab
2024-05-22  1:25 ` dpdklab
2024-05-22  1:26 ` dpdklab
2024-05-22  1:26 ` dpdklab
2024-05-22  1:26 ` dpdklab
2024-05-22  1:26 ` dpdklab
2024-05-22  1:26 ` dpdklab
2024-05-22  1:27 ` dpdklab
2024-05-22  1:27 ` dpdklab
2024-05-22  1:27 ` dpdklab
2024-05-22  1:27 ` dpdklab
2024-05-22  1:27 ` dpdklab
2024-05-22  1:27 ` dpdklab
2024-05-22  1:28 ` dpdklab
2024-05-22  1:29 ` dpdklab
2024-05-22  1:31 ` dpdklab
2024-05-22  1:32 ` dpdklab
2024-05-22  1:33 ` dpdklab
2024-05-22  1:33 ` dpdklab
2024-05-22  1:34 ` dpdklab
2024-05-22  1:35 ` dpdklab
2024-05-22  1:36 ` dpdklab
2024-05-22  1:36 ` dpdklab
2024-05-22  1:39 ` dpdklab
2024-05-22  1:39 ` dpdklab
2024-05-22  1:40 ` dpdklab
2024-05-22  1:43 ` dpdklab
2024-05-22  1:43 ` dpdklab
2024-05-22  1:44 ` dpdklab
2024-05-22  1:46 ` dpdklab
2024-05-22  1:50 ` dpdklab
2024-05-22  1:50 ` dpdklab
2024-05-22  1:54 ` dpdklab
2024-05-22  2:07 ` dpdklab
2024-05-22  2:10 ` dpdklab
2024-05-22  2:13 ` dpdklab
2024-05-22  2:27 ` dpdklab
2024-05-22  2:43 ` dpdklab
2024-05-22  3:51 ` dpdklab
2024-05-23  6:07 ` 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=664d488c.050a0220.ee9a8.de00SMTPIN_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).