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| [GIT MASTER] 31d72ff4dc7c057366153e9918ac92bf9123a3bc
Date: Tue, 13 Feb 2024 17:23:35 -0800 (PST)	[thread overview]
Message-ID: <65cc1617.0d0a0220.96019.8f18SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Functional Testing PASS_

Branch: dpdk

31d72ff4dc7c057366153e9918ac92bf9123a3bc --> functional testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.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/tarballs/27997/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-14  1:23 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-14  1:23 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-14  8:34 dpdklab
2024-02-14  6:49 dpdklab
2024-02-14  6:14 dpdklab
2024-02-14  4:35 dpdklab
2024-02-14  4:14 dpdklab
2024-02-14  4:01 dpdklab
2024-02-14  3:45 dpdklab
2024-02-14  3:25 dpdklab
2024-02-14  3:25 dpdklab
2024-02-14  3:24 dpdklab
2024-02-14  3:16 dpdklab
2024-02-14  3:10 dpdklab
2024-02-14  3:09 dpdklab
2024-02-14  3:08 dpdklab
2024-02-14  3:08 dpdklab
2024-02-14  3:07 dpdklab
2024-02-14  3:07 dpdklab
2024-02-14  3:07 dpdklab
2024-02-14  3:06 dpdklab
2024-02-14  3:06 dpdklab
2024-02-14  3:04 dpdklab
2024-02-14  2:57 dpdklab
2024-02-14  2:57 dpdklab
2024-02-14  2:57 dpdklab
2024-02-14  2:56 dpdklab
2024-02-14  2:52 dpdklab
2024-02-14  2:51 dpdklab
2024-02-14  2:49 dpdklab
2024-02-14  2:49 dpdklab
2024-02-14  2:48 dpdklab
2024-02-14  2:46 dpdklab
2024-02-14  2:46 dpdklab
2024-02-14  2:41 dpdklab
2024-02-14  2:40 dpdklab
2024-02-14  2:40 dpdklab
2024-02-14  2:40 dpdklab
2024-02-14  2:40 dpdklab
2024-02-14  1:50 dpdklab
2024-02-14  1:38 dpdklab
2024-02-14  1:35 dpdklab
2024-02-14  1:34 dpdklab
2024-02-14  1:33 dpdklab
2024-02-14  1:30 dpdklab
2024-02-14  1:29 dpdklab
2024-02-14  1:28 dpdklab
2024-02-14  1:26 dpdklab
2024-02-14  1:25 dpdklab
2024-02-14  1:25 dpdklab
2024-02-14  1:25 dpdklab
2024-02-14  1:23 dpdklab
2024-02-14  1:22 dpdklab
2024-02-14  1:21 dpdklab
2024-02-14  1:21 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=65cc1617.0d0a0220.96019.8f18SMTPIN_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).