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| pw137330 [PATCH] dumpcap: correctly disable promiscuous mo
Date: Thu, 29 Feb 2024 01:44:41 -0800 (PST)	[thread overview]
Message-ID: <65e05209.630a0220.6cd6e.2760SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227092326.340229-1-iboukris@gmail.com>

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

_Functional Testing PASS_

Submitter: Isaac Boukris <iboukris@gmail.com>
Date: Tuesday, February 27 2024 09:23:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137330 --> 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


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.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/1


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-29  9:44 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227092326.340229-1-iboukris@gmail.com>
2024-02-27  9:00 ` |SUCCESS| pw137330 [PATCH] dumpcap: correctly disable promiscuous mode at exit qemudev
2024-02-27  9:05 ` qemudev
2024-02-27  9:23 ` |WARNING| " checkpatch
2024-02-27 10:25 ` |SUCCESS| " 0-day Robot
2024-02-27 22:10 ` |SUCCESS| pw137330 [PATCH] dumpcap: correctly disable promiscuous mo dpdklab
2024-02-28  5:11 ` dpdklab
2024-02-28  6:26 ` dpdklab
2024-02-28  6:33 ` dpdklab
2024-02-28 13:08 ` dpdklab
2024-02-29  9:29 ` dpdklab
2024-02-29  9:34 ` dpdklab
2024-02-29  9:39 ` dpdklab
2024-02-29  9:44 ` dpdklab [this message]
2024-02-27 19:18 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 18:52 dpdklab
2024-02-27 18:18 dpdklab
2024-02-27 18:10 dpdklab
2024-02-27 18:10 dpdklab
2024-02-27 18:08 dpdklab
2024-02-27 18:08 dpdklab
2024-02-27 18:07 dpdklab
2024-02-27 18:05 dpdklab
2024-02-27 18:04 dpdklab
2024-02-27 18:03 dpdklab
2024-02-27 17:59 dpdklab
2024-02-27 17:59 dpdklab
2024-02-27 17:58 dpdklab
2024-02-27 17:58 dpdklab
2024-02-27 17:58 dpdklab
2024-02-27 17:58 dpdklab
2024-02-27 17:56 dpdklab
2024-02-27 17:55 dpdklab
2024-02-27 17:54 dpdklab
2024-02-27 17:54 dpdklab
2024-02-27 17:54 dpdklab
2024-02-27 17:53 dpdklab
2024-02-27 17:53 dpdklab
2024-02-27 17:53 dpdklab
2024-02-27 17:52 dpdklab
2024-02-27 17:41 dpdklab
2024-02-27 17:39 dpdklab
2024-02-27 17:38 dpdklab
2024-02-27 17:38 dpdklab
2024-02-27 17:36 dpdklab
2024-02-27 17:34 dpdklab
2024-02-27 17:34 dpdklab
2024-02-27 17:33 dpdklab
2024-02-27 17:32 dpdklab
2024-02-27 17:32 dpdklab
2024-02-27 17:32 dpdklab
2024-02-27 17:31 dpdklab
2024-02-27 17:31 dpdklab
2024-02-27 17:31 dpdklab
2024-02-27 17:31 dpdklab
2024-02-27 17:30 dpdklab
2024-02-27 17:20 dpdklab
2024-02-27 17:15 dpdklab
2024-02-27 17:13 dpdklab
2024-02-27 13:46 dpdklab
2024-02-27 13:37 dpdklab
2024-02-27 13:36 dpdklab
2024-02-27 13:31 dpdklab
2024-02-27 13:30 dpdklab
2024-02-27 13:29 dpdklab
2024-02-27 13:28 dpdklab
2024-02-27 13:27 dpdklab
2024-02-27 13:15 dpdklab
2024-02-27 13:14 dpdklab
2024-02-27 13:11 dpdklab
2024-02-27 13:09 dpdklab
2024-02-27 12:55 dpdklab
2024-02-27 12:52 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=65e05209.630a0220.6cd6e.2760SMTPIN_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).