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| pw130447-130446 [PATCH] [v5,4/4] build: enable MSVC specif
Date: Fri, 18 Aug 2023 02:35:33 -0700 (PDT)	[thread overview]
Message-ID: <64df3b65.050a0220.47d39.6f9aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, August 16 2023 21:56:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:971d2b57972919527e27ed683032a71864a2eb56

130447-130446 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-18  9:35 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-18  9:35 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-18 10:46 dpdklab
2023-08-18 10:11 dpdklab
2023-08-18  9:35 dpdklab
2023-08-18  9:23 dpdklab
2023-08-18  0:25 dpdklab
2023-08-17  9:46 dpdklab
2023-08-17  9:45 dpdklab
2023-08-17  9:36 dpdklab
2023-08-17  9:31 dpdklab
2023-08-17  9:28 dpdklab
2023-08-17  9:26 dpdklab
2023-08-17  9:23 dpdklab
2023-08-17  9:21 dpdklab
2023-08-17  9:19 dpdklab
2023-08-17  9:17 dpdklab
2023-08-17  9:15 dpdklab
2023-08-17  9:15 dpdklab
2023-08-17  9:15 dpdklab
2023-08-17  9:14 dpdklab
2023-08-17  9:07 dpdklab
2023-08-17  9:04 dpdklab
2023-08-17  8:57 dpdklab
2023-08-17  8:54 dpdklab
2023-08-17  8:54 dpdklab
2023-08-17  8:52 dpdklab
2023-08-17  8:45 dpdklab
2023-08-17  8:39 dpdklab
2023-08-17  8:39 dpdklab
2023-08-17  8:37 dpdklab
2023-08-17  8:37 dpdklab
2023-08-17  8:34 dpdklab
2023-08-17  8:33 dpdklab
2023-08-17  8:32 dpdklab
2023-08-17  8:31 dpdklab
2023-08-17  8:30 dpdklab
2023-08-17  8:28 dpdklab
2023-08-17  8:23 dpdklab
2023-08-17  8:16 dpdklab
2023-08-17  8:07 dpdklab
2023-08-17  7:58 dpdklab
2023-08-17  7:56 dpdklab
2023-08-17  7:53 dpdklab
2023-08-17  7:51 dpdklab
2023-08-17  7:50 dpdklab
2023-08-17  7:47 dpdklab
2023-08-17  7:46 dpdklab
2023-08-17  7:44 dpdklab
2023-08-17  7:43 dpdklab
2023-08-17  7:42 dpdklab
2023-08-17  7:39 dpdklab
2023-08-17  7:35 dpdklab
2023-08-17  7:34 dpdklab
2023-08-17  7:33 dpdklab
2023-08-17  7:33 dpdklab
2023-08-17  7:32 dpdklab
2023-08-17  7:31 dpdklab
2023-08-17  7:30 dpdklab
2023-08-17  7:30 dpdklab
2023-08-17  7:29 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=64df3b65.050a0220.47d39.6f9aSMTPIN_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).