From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw126849 [PATCH] [v4] net/iavf: add devargs to control watchdog
Date: Mon, 15 May 2023 01:26:46 -0700 (PDT) [thread overview]
Message-ID: <6461ecc6.050a0220.559cc.04adSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/126849
_Functional Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Monday, May 15 2023 06:54:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dbff181d62c997f128b75db2bbac9f42e8dd0f8f
126849 --> functional testing pass
Test environment and result as below:
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
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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26224/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-15 8:26 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 8:26 dpdklab [this message]
[not found] <20230515065405.795497-1-zhichaox.zeng@intel.com>
2023-05-15 6:49 ` |SUCCESS| pw126849 [PATCH v4] " checkpatch
2023-05-15 8:00 ` 0-day Robot
2023-05-16 1:33 ` qemudev
2023-05-16 1:34 ` qemudev
-- strict thread matches above, loose matches on Subject: below --
2023-05-15 17:16 |SUCCESS| pw126849 [PATCH] [v4] " dpdklab
2023-05-15 9:35 dpdklab
2023-05-15 9:23 dpdklab
2023-05-15 9:18 dpdklab
2023-05-15 9:12 dpdklab
2023-05-15 9:11 dpdklab
2023-05-15 9:11 dpdklab
2023-05-15 9:03 dpdklab
2023-05-15 9:00 dpdklab
2023-05-15 8:59 dpdklab
2023-05-15 8:55 dpdklab
2023-05-15 8:54 dpdklab
2023-05-15 8:48 dpdklab
2023-05-15 8:43 dpdklab
2023-05-15 8:40 dpdklab
2023-05-15 8:38 dpdklab
2023-05-15 8:37 dpdklab
2023-05-15 8:37 dpdklab
2023-05-15 8:34 dpdklab
2023-05-15 8:25 dpdklab
2023-05-15 8:20 dpdklab
2023-05-15 8:19 dpdklab
2023-05-15 8:18 dpdklab
2023-05-15 8:18 dpdklab
2023-05-15 8:18 dpdklab
2023-05-15 8:17 dpdklab
2023-05-15 8:12 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=6461ecc6.050a0220.559cc.04adSMTPIN_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).