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| pw136851 [PATCH] examples/l3fwd: fix conf propagation to R
Date: Fri, 16 Feb 2024 04:51:21 -0800 (PST)	[thread overview]
Message-ID: <65cf5a49.5d0a0220.37dbf.88b5SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Kamil Vojanec <vojanec@cesnet.cz>
Date: Friday, February 16 2024 12:02:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:537caad2c70057c68e110211bab0cb4088f391d2

136851 --> 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/3


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-16 12:51 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 12:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-16 16:38 dpdklab
2024-02-16 16:31 dpdklab
2024-02-16 14:35 dpdklab
2024-02-16 14:35 dpdklab
2024-02-16 14:30 dpdklab
2024-02-16 14:25 dpdklab
2024-02-16 14:22 dpdklab
2024-02-16 13:52 dpdklab
2024-02-16 13:47 dpdklab
2024-02-16 13:39 dpdklab
2024-02-16 13:38 dpdklab
2024-02-16 13:37 dpdklab
2024-02-16 13:36 dpdklab
2024-02-16 13:34 dpdklab
2024-02-16 13:32 dpdklab
2024-02-16 13:31 dpdklab
2024-02-16 13:27 dpdklab
2024-02-16 13:25 dpdklab
2024-02-16 13:25 dpdklab
2024-02-16 13:23 dpdklab
2024-02-16 13:23 dpdklab
2024-02-16 13:21 dpdklab
2024-02-16 13:20 dpdklab
2024-02-16 13:19 dpdklab
2024-02-16 13:17 dpdklab
2024-02-16 13:17 dpdklab
2024-02-16 13:17 dpdklab
2024-02-16 13:14 dpdklab
2024-02-16 13:13 dpdklab
2024-02-16 13:09 dpdklab
2024-02-16 13:08 dpdklab
2024-02-16 13:07 dpdklab
2024-02-16 13:07 dpdklab
2024-02-16 13:06 dpdklab
2024-02-16 13:06 dpdklab
2024-02-16 13:06 dpdklab
2024-02-16 13:06 dpdklab
2024-02-16 13:05 dpdklab
2024-02-16 13:05 dpdklab
2024-02-16 13:04 dpdklab
2024-02-16 13:03 dpdklab
2024-02-16 13:02 dpdklab
2024-02-16 13:02 dpdklab
2024-02-16 13:01 dpdklab
2024-02-16 13:01 dpdklab
2024-02-16 13:01 dpdklab
2024-02-16 12:58 dpdklab
2024-02-16 12:57 dpdklab
2024-02-16 12:55 dpdklab
2024-02-16 12:54 dpdklab
2024-02-16 12:53 dpdklab
2024-02-16 12:52 dpdklab
2024-02-16 12:52 dpdklab
2024-02-16 12:52 dpdklab
2024-02-16 12:51 dpdklab
2024-02-16 12:51 dpdklab
2024-02-16 12:51 dpdklab
2024-02-16 12:51 dpdklab
2024-02-16 12:50 dpdklab
2024-02-16 12:49 dpdklab
2024-02-16 12:48 dpdklab
2024-02-16 12:45 dpdklab
2024-02-16 12:45 dpdklab
2024-02-16 12:43 dpdklab
2024-02-16 12:43 dpdklab
2024-02-16 12:37 dpdklab
2024-02-16 12:36 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=65cf5a49.5d0a0220.37dbf.88b5SMTPIN_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).