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| pw136111-136118 [PATCH] [v2,8/8] net/sfc: fix calloc param
Date: Wed, 24 Jan 2024 16:02:49 -0800 (PST)	[thread overview]
Message-ID: <65b1a529.050a0220.1f3b6.59b1SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Wednesday, January 24 2024 18:54:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1

136111-136118 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
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: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-25  0:02 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  0:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-26 16:56 dpdklab
2024-01-26 16:52 dpdklab
2024-01-25  4:24 dpdklab
2024-01-25  1:57 dpdklab
2024-01-25  1:38 dpdklab
2024-01-25  1:36 dpdklab
2024-01-25  1:24 dpdklab
2024-01-25  1:22 dpdklab
2024-01-25  1:20 dpdklab
2024-01-25  1:19 dpdklab
2024-01-25  1:17 dpdklab
2024-01-25  1:16 dpdklab
2024-01-25  1:13 dpdklab
2024-01-25  1:13 dpdklab
2024-01-25  1:09 dpdklab
2024-01-25  1:09 dpdklab
2024-01-25  1:07 dpdklab
2024-01-25  1:07 dpdklab
2024-01-25  1:05 dpdklab
2024-01-25  1:04 dpdklab
2024-01-25  1:04 dpdklab
2024-01-25  1:04 dpdklab
2024-01-25  1:03 dpdklab
2024-01-25  1:02 dpdklab
2024-01-25  1:02 dpdklab
2024-01-25  1:02 dpdklab
2024-01-25  1:01 dpdklab
2024-01-25  0:56 dpdklab
2024-01-25  0:48 dpdklab
2024-01-25  0:43 dpdklab
2024-01-25  0:42 dpdklab
2024-01-25  0:42 dpdklab
2024-01-25  0:42 dpdklab
2024-01-25  0:41 dpdklab
2024-01-25  0:41 dpdklab
2024-01-25  0:41 dpdklab
2024-01-25  0:41 dpdklab
2024-01-25  0:40 dpdklab
2024-01-25  0:40 dpdklab
2024-01-25  0:40 dpdklab
2024-01-25  0:40 dpdklab
2024-01-25  0:39 dpdklab
2024-01-25  0:39 dpdklab
2024-01-25  0:39 dpdklab
2024-01-25  0:39 dpdklab
2024-01-25  0:38 dpdklab
2024-01-25  0:38 dpdklab
2024-01-25  0:38 dpdklab
2024-01-25  0:37 dpdklab
2024-01-25  0:37 dpdklab
2024-01-25  0:37 dpdklab
2024-01-25  0:36 dpdklab
2024-01-25  0:35 dpdklab
2024-01-25  0:27 dpdklab
2024-01-25  0:25 dpdklab
2024-01-25  0:24 dpdklab
2024-01-25  0:24 dpdklab
2024-01-25  0:23 dpdklab
2024-01-25  0:12 dpdklab
2024-01-25  0:11 dpdklab
2024-01-25  0:10 dpdklab
2024-01-25  0:03 dpdklab
2024-01-24 23:52 dpdklab
2024-01-24 23:51 dpdklab
2024-01-24 23:51 dpdklab
2024-01-24 23:45 dpdklab
2024-01-24 23:44 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=65b1a529.050a0220.1f3b6.59b1SMTPIN_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).