From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138659 [PATCH] net/vmxnet3: Don't enable rx queue interr
Date: Thu, 21 Mar 2024 14:58:46 -0700 (PDT) [thread overview]
Message-ID: <65fcad96.170a0220.df855.1b98SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240321103133.1531-1-thj@freebsd.org>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138659
_Functional Testing PASS_
Submitter: Tom Jones <thj@freebsd.org>
Date: Thursday, March 21 2024 10:31:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c7f6bdc5942d8827c46710a83f9288ce5e3c9458
138659 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
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.83+
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/29623/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-21 21:58 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240321103133.1531-1-thj@freebsd.org>
2024-03-21 10:12 ` |SUCCESS| pw138659 [PATCH] net/vmxnet3: Don't enable rx queue interrupts on FreeBSD qemudev
2024-03-21 10:16 ` qemudev
2024-03-21 10:35 ` checkpatch
2024-03-21 11:24 ` 0-day Robot
2024-03-21 20:41 ` |SUCCESS| pw138659 [PATCH] net/vmxnet3: Don't enable rx queue interr dpdklab
2024-03-21 20:42 ` dpdklab
2024-03-21 20:50 ` dpdklab
2024-03-21 20:50 ` dpdklab
2024-03-21 20:50 ` dpdklab
2024-03-21 21:02 ` dpdklab
2024-03-21 21:03 ` dpdklab
2024-03-21 21:04 ` dpdklab
2024-03-21 21:04 ` dpdklab
2024-03-21 21:05 ` dpdklab
2024-03-21 21:05 ` dpdklab
2024-03-21 21:14 ` dpdklab
2024-03-21 21:19 ` dpdklab
2024-03-21 21:20 ` dpdklab
2024-03-21 21:20 ` dpdklab
2024-03-21 21:21 ` dpdklab
2024-03-21 21:36 ` dpdklab
2024-03-21 21:47 ` dpdklab
2024-03-21 21:48 ` dpdklab
2024-03-21 21:49 ` dpdklab
2024-03-21 21:50 ` dpdklab
2024-03-21 21:58 ` dpdklab [this message]
2024-03-21 22:00 ` dpdklab
2024-03-21 22:00 ` dpdklab
2024-03-21 22:01 ` dpdklab
2024-03-21 22:02 ` dpdklab
2024-03-21 22:02 ` dpdklab
2024-03-21 22:03 ` dpdklab
2024-03-21 22:03 ` dpdklab
2024-03-21 22:04 ` dpdklab
2024-03-21 22:06 ` dpdklab
2024-03-21 22:07 ` dpdklab
2024-03-21 22:09 ` dpdklab
2024-03-21 22:14 ` dpdklab
2024-03-21 22:14 ` dpdklab
2024-03-21 22:15 ` dpdklab
2024-03-21 22:15 ` dpdklab
2024-03-21 22:16 ` dpdklab
2024-03-21 22:16 ` dpdklab
2024-03-21 22:16 ` dpdklab
2024-03-21 22:17 ` dpdklab
2024-03-21 22:17 ` dpdklab
2024-03-21 22:18 ` dpdklab
2024-03-21 22:18 ` dpdklab
2024-03-21 22:18 ` dpdklab
2024-03-21 22:19 ` dpdklab
2024-03-21 22:19 ` dpdklab
2024-03-21 22:19 ` dpdklab
2024-03-21 22:19 ` dpdklab
2024-03-21 22:20 ` dpdklab
2024-03-21 22:20 ` dpdklab
2024-03-21 22:21 ` dpdklab
2024-03-21 22:22 ` dpdklab
2024-03-21 22:22 ` dpdklab
2024-03-21 22:22 ` dpdklab
2024-03-21 22:22 ` dpdklab
2024-03-21 22:23 ` dpdklab
2024-03-21 22:23 ` dpdklab
2024-03-21 22:23 ` dpdklab
2024-03-21 22:23 ` dpdklab
2024-03-21 22:24 ` dpdklab
2024-03-21 22:24 ` dpdklab
2024-03-21 22:24 ` dpdklab
2024-03-21 22:25 ` dpdklab
2024-03-21 22:26 ` dpdklab
2024-03-21 22:26 ` dpdklab
2024-03-21 22:26 ` dpdklab
2024-03-21 22:27 ` dpdklab
2024-03-21 22:27 ` dpdklab
2024-03-21 22:27 ` dpdklab
2024-03-21 22:48 ` dpdklab
2024-03-21 22:57 ` dpdklab
2024-03-21 23:07 ` dpdklab
2024-03-21 23:10 ` dpdklab
2024-03-22 3:52 ` dpdklab
2024-03-23 14:55 ` dpdklab
2024-03-23 15:31 ` 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=65fcad96.170a0220.df855.1b98SMTPIN_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).