From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126206 [PATCH] net/iavf: add devargs to enable watchdog
Date: Tue, 18 Apr 2023 07:15:19 +0000 (UTC) [thread overview]
Message-ID: <20230418071519.BE0B560095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126206
_Testing PASS_
Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Tuesday, April 18 2023 05:42:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126206 --> testing pass
Test environment and result as below:
+----------------------+---------------------------+------------------------------+--------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | lpm_autotest |
+======================+===========================+==============================+==============+
| Debian 11 | PASS | PASS | SKIPPED |
+----------------------+---------------------------+------------------------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | SKIPPED | PASS |
+----------------------+---------------------------+------------------------------+--------------+
Debian 11
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26023/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-18 7:15 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 7:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 17:07 dpdklab
2023-04-18 17:07 dpdklab
2023-04-18 15:24 dpdklab
2023-04-18 15:24 dpdklab
2023-04-18 12:02 dpdklab
2023-04-18 12:01 dpdklab
2023-04-18 10:30 dpdklab
2023-04-18 10:27 dpdklab
2023-04-18 8:20 dpdklab
2023-04-18 7:56 dpdklab
2023-04-18 7:40 dpdklab
2023-04-18 7:36 dpdklab
2023-04-18 7:35 dpdklab
2023-04-18 7:24 dpdklab
2023-04-18 7:24 dpdklab
2023-04-18 7:24 dpdklab
2023-04-18 7:23 dpdklab
2023-04-18 7:19 dpdklab
2023-04-18 7:14 dpdklab
2023-04-18 7:13 dpdklab
2023-04-18 7:08 dpdklab
2023-04-18 7:08 dpdklab
2023-04-18 7:03 dpdklab
2023-04-18 7:00 dpdklab
2023-04-18 6:58 dpdklab
2023-04-18 6:57 dpdklab
2023-04-18 6:56 dpdklab
2023-04-18 6:54 dpdklab
2023-04-18 6:52 dpdklab
2023-04-18 6:51 dpdklab
2023-04-18 6:50 dpdklab
2023-04-18 6:48 dpdklab
2023-04-18 6:47 dpdklab
2023-04-18 6:45 dpdklab
2023-04-18 6:44 dpdklab
2023-04-18 6:43 dpdklab
2023-04-18 6:42 dpdklab
2023-04-18 6:35 dpdklab
2023-04-18 6:35 dpdklab
2023-04-18 6:33 dpdklab
2023-04-18 6:32 dpdklab
2023-04-18 6:31 dpdklab
2023-04-18 6:31 dpdklab
2023-04-18 6:29 dpdklab
2023-04-18 6:26 dpdklab
2023-04-18 6:25 dpdklab
2023-04-18 6:23 dpdklab
2023-04-18 6:22 dpdklab
2023-04-18 6:19 dpdklab
2023-04-18 6:18 dpdklab
2023-04-18 6:16 dpdklab
2023-04-18 6:15 dpdklab
2023-04-18 6:14 dpdklab
2023-04-18 6:11 dpdklab
2023-04-18 6:10 dpdklab
2023-04-18 6:07 dpdklab
2023-04-18 6:03 dpdklab
[not found] <20230418054221.1076945-1-zhichaox.zeng@intel.com>
2023-04-18 5:27 ` qemudev
2023-04-18 5:31 ` qemudev
2023-04-18 5:38 ` checkpatch
2023-04-18 6:39 ` 0-day Robot
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=20230418071519.BE0B560095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).