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| pw135528-135530 [PATCH] [3/3] pipeline: convert to a dynam
Date: Fri, 22 Dec 2023 15:31:04 -0800 (PST)	[thread overview]
Message-ID: <65861c38.170a0220.ce897.8718SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, December 22 2023 17:44:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

135528-135530 --> 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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-22 23:31 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 23:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-23  3:05 dpdklab
2023-12-23  1:56 dpdklab
2023-12-23  1:41 dpdklab
2023-12-23  1:27 dpdklab
2023-12-23  1:21 dpdklab
2023-12-23  1:21 dpdklab
2023-12-23  1:14 dpdklab
2023-12-23  1:11 dpdklab
2023-12-23  1:10 dpdklab
2023-12-23  1:09 dpdklab
2023-12-23  1:07 dpdklab
2023-12-23  1:06 dpdklab
2023-12-23  1:06 dpdklab
2023-12-23  1:05 dpdklab
2023-12-23  1:03 dpdklab
2023-12-23  1:03 dpdklab
2023-12-23  1:02 dpdklab
2023-12-23  1:01 dpdklab
2023-12-23  0:59 dpdklab
2023-12-23  0:57 dpdklab
2023-12-23  0:56 dpdklab
2023-12-23  0:56 dpdklab
2023-12-23  0:55 dpdklab
2023-12-23  0:52 dpdklab
2023-12-23  0:51 dpdklab
2023-12-23  0:50 dpdklab
2023-12-23  0:45 dpdklab
2023-12-23  0:45 dpdklab
2023-12-23  0:45 dpdklab
2023-12-23  0:43 dpdklab
2023-12-23  0:39 dpdklab
2023-12-23  0:39 dpdklab
2023-12-23  0:38 dpdklab
2023-12-23  0:34 dpdklab
2023-12-23  0:33 dpdklab
2023-12-23  0:33 dpdklab
2023-12-23  0:28 dpdklab
2023-12-23  0:26 dpdklab
2023-12-23  0:25 dpdklab
2023-12-23  0:23 dpdklab
2023-12-23  0:22 dpdklab
2023-12-23  0:20 dpdklab
2023-12-23  0:19 dpdklab
2023-12-23  0:18 dpdklab
2023-12-23  0:17 dpdklab
2023-12-23  0:16 dpdklab
2023-12-23  0:12 dpdklab
2023-12-23  0:12 dpdklab
2023-12-23  0:11 dpdklab
2023-12-23  0:11 dpdklab
2023-12-23  0:10 dpdklab
2023-12-23  0:09 dpdklab
2023-12-23  0:06 dpdklab
2023-12-22 23:44 dpdklab
2023-12-22 23:38 dpdklab
2023-12-22 23:34 dpdklab
2023-12-22 23:26 dpdklab
2023-12-22 23:24 dpdklab
2023-12-22 23:18 dpdklab
2023-12-22 23:18 dpdklab
2023-12-22 23:17 dpdklab
2023-12-22 23:16 dpdklab
2023-12-22 23:16 dpdklab
2023-12-22 23:15 dpdklab
2023-12-22 23:13 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=65861c38.170a0220.ce897.8718SMTPIN_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).