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| pw134405-134408 [PATCH] [4/4] examples: add extension keyw
Date: Wed, 15 Nov 2023 15:45:43 -0800 (PST)	[thread overview]
Message-ID: <65555827.170a0220.9753e.f76eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134408

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, November 15 2023 23:02:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92d7ce4afc4a558f27bbc8368823c625f4e0f9dc

134405-134408 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-15 23:45 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 23:45 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-16 23:52 dpdklab
2023-11-16 23:33 dpdklab
2023-11-16  2:29 dpdklab
2023-11-16  2:15 dpdklab
2023-11-16  1:25 dpdklab
2023-11-16  1:03 dpdklab
2023-11-16  1:02 dpdklab
2023-11-16  0:58 dpdklab
2023-11-16  0:55 dpdklab
2023-11-16  0:52 dpdklab
2023-11-16  0:49 dpdklab
2023-11-16  0:48 dpdklab
2023-11-16  0:45 dpdklab
2023-11-16  0:44 dpdklab
2023-11-16  0:15 dpdklab
2023-11-16  0:05 dpdklab
2023-11-16  0:04 dpdklab
2023-11-16  0:02 dpdklab
2023-11-16  0:00 dpdklab
2023-11-15 23:59 dpdklab
2023-11-15 23:59 dpdklab
2023-11-15 23:57 dpdklab
2023-11-15 23:57 dpdklab
2023-11-15 23:56 dpdklab
2023-11-15 23:56 dpdklab
2023-11-15 23:54 dpdklab
2023-11-15 23:53 dpdklab
2023-11-15 23:52 dpdklab
2023-11-15 23:52 dpdklab
2023-11-15 23:51 dpdklab
2023-11-15 23:49 dpdklab
2023-11-15 23:48 dpdklab
2023-11-15 23:47 dpdklab
2023-11-15 23:46 dpdklab
2023-11-15 23:46 dpdklab
2023-11-15 23:45 dpdklab
2023-11-15 23:45 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:44 dpdklab
2023-11-15 23:43 dpdklab
2023-11-15 23:43 dpdklab
2023-11-15 23:43 dpdklab
2023-11-15 23:42 dpdklab
2023-11-15 23:42 dpdklab
2023-11-15 23:42 dpdklab
2023-11-15 23:41 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=65555827.170a0220.9753e.f76eSMTPIN_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).