From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128390 [PATCH] net/iavf: fix virtchnl cmd called in intr
Date: Thu, 08 Jun 2023 13:02:36 -0700 (PDT) [thread overview]
Message-ID: <648233dc.0c0a0220.f939.609dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128390
_Testing PASS_
Submitter: Kaiwen Deng <kaiwenx.deng@intel.com>
Date: Thursday, June 08 2023 07:27:56
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: master
CommitID:0a150adf010e7c4bedbc0d3c44e6e04ba6a78d8e
128390 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Debian Bullseye | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26590/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-08 20:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 20:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 23:05 dpdklab
2023-06-09 3:48 dpdklab
2023-06-09 3:38 dpdklab
2023-06-09 3:33 dpdklab
2023-06-09 3:29 dpdklab
2023-06-09 3:13 dpdklab
2023-06-09 2:32 dpdklab
2023-06-09 2:32 dpdklab
2023-06-08 20:05 dpdklab
2023-06-08 20:05 dpdklab
2023-06-08 20:04 dpdklab
2023-06-08 20:04 dpdklab
2023-06-08 20:03 dpdklab
2023-06-08 20:03 dpdklab
2023-06-08 20:03 dpdklab
2023-06-08 20:03 dpdklab
2023-06-08 20:02 dpdklab
2023-06-08 20:01 dpdklab
2023-06-08 20:01 dpdklab
2023-06-08 19:58 dpdklab
2023-06-08 19:52 dpdklab
2023-06-08 18:47 dpdklab
2023-06-08 18:33 dpdklab
2023-06-08 18:10 dpdklab
2023-06-08 18:07 dpdklab
2023-06-08 18:02 dpdklab
2023-06-08 18:02 dpdklab
2023-06-08 17:58 dpdklab
2023-06-08 17:58 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=648233dc.0c0a0220.f939.609dSMTPIN_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).