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| pw136303 [PATCH] [1/1] eal: add C++ include guard in gener
Date: Thu, 01 Feb 2024 23:48:37 -0800 (PST)	[thread overview]
Message-ID: <65bc9e55.050a0220.98de.5089SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Ashish Sadanandan <ashish.sadanandan@gmail.com>
Date: Friday, February 02 2024 05:13:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a4ce111cc89f580b8c4aad51bdb061acbdfde86b

136303 --> 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: 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/29029/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-02  7:48 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02  7:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-02 14:22 dpdklab
2024-02-02 13:50 dpdklab
2024-02-02 12:51 dpdklab
2024-02-02 10:48 dpdklab
2024-02-02 10:44 dpdklab
2024-02-02 10:38 dpdklab
2024-02-02 10:19 dpdklab
2024-02-02 10:12 dpdklab
2024-02-02 10:05 dpdklab
2024-02-02 10:03 dpdklab
2024-02-02 10:03 dpdklab
2024-02-02 10:02 dpdklab
2024-02-02  9:58 dpdklab
2024-02-02  9:57 dpdklab
2024-02-02  9:56 dpdklab
2024-02-02  9:56 dpdklab
2024-02-02  9:55 dpdklab
2024-02-02  9:55 dpdklab
2024-02-02  9:54 dpdklab
2024-02-02  9:48 dpdklab
2024-02-02  9:44 dpdklab
2024-02-02  9:42 dpdklab
2024-02-02  9:35 dpdklab
2024-02-02  9:34 dpdklab
2024-02-02  9:33 dpdklab
2024-02-02  9:31 dpdklab
2024-02-02  9:31 dpdklab
2024-02-02  9:24 dpdklab
2024-02-02  9:24 dpdklab
2024-02-02  9:24 dpdklab
2024-02-02  9:24 dpdklab
2024-02-02  9:19 dpdklab
2024-02-02  9:18 dpdklab
2024-02-02  9:18 dpdklab
2024-02-02  9:17 dpdklab
2024-02-02  9:17 dpdklab
2024-02-02  9:16 dpdklab
2024-02-02  9:15 dpdklab
2024-02-02  9:15 dpdklab
2024-02-02  9:15 dpdklab
2024-02-02  9:15 dpdklab
2024-02-02  9:15 dpdklab
2024-02-02  9:14 dpdklab
2024-02-02  9:14 dpdklab
2024-02-02  9:14 dpdklab
2024-02-02  9:14 dpdklab
2024-02-02  9:13 dpdklab
2024-02-02  9:12 dpdklab
2024-02-02  8:58 dpdklab
2024-02-02  8:57 dpdklab
2024-02-02  8:45 dpdklab
2024-02-02  8:38 dpdklab
2024-02-02  8:36 dpdklab
2024-02-02  8:36 dpdklab
2024-02-02  8:35 dpdklab
2024-02-02  8:34 dpdklab
2024-02-02  8:00 dpdklab
2024-02-02  7:59 dpdklab
2024-02-02  7:58 dpdklab
2024-02-02  7:58 dpdklab
2024-02-02  7:56 dpdklab
2024-02-02  7:56 dpdklab
2024-02-02  7:55 dpdklab
2024-02-02  7:55 dpdklab
2024-02-02  7:55 dpdklab
2024-02-02  7:54 dpdklab
2024-02-02  7:48 dpdklab
2024-02-02  7:28 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=65bc9e55.050a0220.98de.5089SMTPIN_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).