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| pw137646 [PATCH] app/dumpcap:fix coredump problem because
Date: Mon, 04 Mar 2024 07:31:57 -0800 (PST)	[thread overview]
Message-ID: <65e5e96d.d40a0220.52df2.3081SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301104129.3725-1-laitianli@tom.com>

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

_Functional Testing PASS_

Submitter: Tianli Lai <laitianli@tom.com>
Date: Friday, March 01 2024 10:41:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137646 --> 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/29355/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-04 15:32 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301104129.3725-1-laitianli@tom.com>
2024-03-01  2:19 ` |SUCCESS| pw137646 [PATCH] app/dumpcap:fix coredump problem because pcap_dump 3th argument is null qemudev
2024-03-01  2:24 ` qemudev
2024-03-01  2:42 ` checkpatch
2024-03-01  3:45 ` 0-day Robot
2024-03-01  4:17 ` |SUCCESS| pw137646 [PATCH] app/dumpcap:fix coredump problem because dpdklab
2024-03-01  4:20 ` dpdklab
2024-03-01  4:20 ` dpdklab
2024-03-01  4:21 ` dpdklab
2024-03-01  4:31 ` dpdklab
2024-03-01  4:33 ` dpdklab
2024-03-01  4:34 ` dpdklab
2024-03-01  4:35 ` dpdklab
2024-03-01  4:36 ` dpdklab
2024-03-01  4:36 ` dpdklab
2024-03-01  4:37 ` dpdklab
2024-03-01  4:47 ` dpdklab
2024-03-01  4:47 ` dpdklab
2024-03-01  4:47 ` dpdklab
2024-03-01  4:48 ` dpdklab
2024-03-01  4:50 ` dpdklab
2024-03-01  4:50 ` dpdklab
2024-03-01  5:33 ` dpdklab
2024-03-01  5:33 ` dpdklab
2024-03-01  5:34 ` dpdklab
2024-03-01  5:34 ` dpdklab
2024-03-01  5:34 ` dpdklab
2024-03-01  5:35 ` dpdklab
2024-03-01  5:35 ` dpdklab
2024-03-01  5:35 ` dpdklab
2024-03-01  5:35 ` dpdklab
2024-03-01  5:35 ` dpdklab
2024-03-01  5:36 ` dpdklab
2024-03-01  5:36 ` dpdklab
2024-03-01  5:36 ` dpdklab
2024-03-01  5:36 ` dpdklab
2024-03-01  5:37 ` dpdklab
2024-03-01  5:37 ` dpdklab
2024-03-01  5:37 ` dpdklab
2024-03-01  5:37 ` dpdklab
2024-03-01  5:37 ` dpdklab
2024-03-01  5:38 ` dpdklab
2024-03-01  5:38 ` dpdklab
2024-03-01  5:38 ` dpdklab
2024-03-01  5:39 ` dpdklab
2024-03-01  5:39 ` dpdklab
2024-03-01  5:40 ` dpdklab
2024-03-01  5:40 ` dpdklab
2024-03-01  5:40 ` dpdklab
2024-03-01  5:40 ` dpdklab
2024-03-01  5:40 ` dpdklab
2024-03-01  5:41 ` dpdklab
2024-03-01  5:42 ` dpdklab
2024-03-01  5:42 ` dpdklab
2024-03-01  5:42 ` dpdklab
2024-03-01  5:42 ` dpdklab
2024-03-01  5:43 ` dpdklab
2024-03-01  5:43 ` dpdklab
2024-03-01  5:44 ` dpdklab
2024-03-01  5:44 ` dpdklab
2024-03-01  5:58 ` dpdklab
2024-03-01  5:58 ` dpdklab
2024-03-01  6:02 ` dpdklab
2024-03-01  6:15 ` dpdklab
2024-03-01  6:49 ` dpdklab
2024-03-01  8:14 ` dpdklab
2024-03-01  9:56 ` dpdklab
2024-03-01 16:01 ` dpdklab
2024-03-01 16:06 ` dpdklab
2024-03-01 16:08 ` dpdklab
2024-03-01 16:13 ` dpdklab
2024-03-02  4:18 ` dpdklab
2024-03-02  4:27 ` dpdklab
2024-03-02 15:40 ` dpdklab
2024-03-02 18:25 ` dpdklab
2024-03-02 18:33 ` dpdklab
2024-03-04 14:59 ` dpdklab
2024-03-04 15:31 ` dpdklab [this message]
2024-03-04 18:05 ` 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=65e5e96d.d40a0220.52df2.3081SMTPIN_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).