From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138372-138374 [PATCH] [3/3] net/vdev: fix insert vdev co
Date: Sun, 17 Mar 2024 20:09:17 -0700 (PDT) [thread overview]
Message-ID: <65f7b05d.050a0220.e27e6.1b65SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314093630.1066948-4-mingjinx.ye@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138374
_Functional Testing PASS_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Thursday, March 14 2024 09:36:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3
138372-138374 --> 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
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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29546/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-03-18 3:09 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314093630.1066948-4-mingjinx.ye@intel.com>
2024-03-14 9:32 ` |SUCCESS| pw138372-138374 [PATCH 3/3] net/vdev: fix insert vdev core dump qemudev
2024-03-14 9:36 ` qemudev
2024-03-14 9:56 ` |SUCCESS| pw138374 " checkpatch
2024-03-14 10:42 ` |SUCCESS| pw138372-138374 [PATCH] [3/3] net/vdev: fix insert vdev co dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:42 ` dpdklab
2024-03-14 10:43 ` dpdklab
2024-03-14 10:43 ` |SUCCESS| pw138374 [PATCH 3/3] net/vdev: fix insert vdev core dump 0-day Robot
2024-03-14 10:43 ` |SUCCESS| pw138372-138374 [PATCH] [3/3] net/vdev: fix insert vdev co dpdklab
2024-03-14 10:43 ` dpdklab
2024-03-14 10:44 ` dpdklab
2024-03-14 10:44 ` dpdklab
2024-03-14 10:45 ` dpdklab
2024-03-14 10:49 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:50 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 10:51 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:52 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:53 ` dpdklab
2024-03-14 10:54 ` dpdklab
2024-03-14 10:54 ` dpdklab
2024-03-14 10:55 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:56 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:58 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 10:59 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:00 ` dpdklab
2024-03-14 11:01 ` dpdklab
2024-03-14 11:01 ` dpdklab
2024-03-14 11:02 ` dpdklab
2024-03-14 11:10 ` dpdklab
2024-03-14 11:11 ` dpdklab
2024-03-14 11:11 ` dpdklab
2024-03-14 11:41 ` dpdklab
2024-03-14 11:42 ` dpdklab
2024-03-14 11:53 ` dpdklab
2024-03-14 11:53 ` dpdklab
2024-03-14 12:26 ` dpdklab
2024-03-18 2:33 ` dpdklab
2024-03-18 3:09 ` dpdklab [this message]
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=65f7b05d.050a0220.e27e6.1b65SMTPIN_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).