From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131227 [PATCH] [v4] net/iavf: unregister intr handler be
Date: Fri, 08 Sep 2023 03:50:01 -0700 (PDT) [thread overview]
Message-ID: <64fafc59.170a0220.5baec.2f2cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131227
_Testing PASS_
Submitter: Saurabh Singhal <saurabhs@arista.com>
Date: Thursday, September 07 2023 03:15:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e92ba1426914db1d224dd5e9a1743657681b8814
131227 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27546/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-08 10:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 10:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-08 11:59 dpdklab
2023-09-08 11:07 dpdklab
2023-09-08 11:07 dpdklab
2023-09-08 11:01 dpdklab
2023-09-08 10:57 dpdklab
2023-09-08 10:55 dpdklab
2023-09-08 10:53 dpdklab
2023-09-08 10:51 dpdklab
2023-09-08 10:47 dpdklab
2023-09-08 10:46 dpdklab
2023-09-08 10:32 dpdklab
2023-09-08 10:29 dpdklab
2023-09-08 10:25 dpdklab
2023-09-08 10:07 dpdklab
2023-09-08 10:05 dpdklab
2023-09-08 9:59 dpdklab
2023-09-08 9:57 dpdklab
2023-09-08 9:56 dpdklab
2023-09-08 9:55 dpdklab
2023-09-08 9:54 dpdklab
2023-09-08 9:53 dpdklab
2023-09-08 9:53 dpdklab
2023-09-08 9:52 dpdklab
2023-09-08 9:52 dpdklab
2023-09-08 9:51 dpdklab
2023-09-08 9:51 dpdklab
2023-09-08 9:51 dpdklab
2023-09-08 9:49 dpdklab
2023-09-08 9:48 dpdklab
2023-09-08 9:45 dpdklab
2023-09-08 9:45 dpdklab
2023-09-08 8:07 dpdklab
2023-09-08 7:52 dpdklab
2023-09-08 7:29 dpdklab
2023-09-08 7:19 dpdklab
2023-09-08 7:15 dpdklab
2023-09-08 7:14 dpdklab
2023-09-08 7:09 dpdklab
2023-09-08 7:05 dpdklab
2023-09-08 6:08 dpdklab
2023-09-08 6:05 dpdklab
2023-09-08 6:02 dpdklab
2023-09-08 6:01 dpdklab
2023-09-08 5:59 dpdklab
2023-09-08 5:58 dpdklab
2023-09-08 5:57 dpdklab
2023-09-08 5:57 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=64fafc59.170a0220.5baec.2f2cSMTPIN_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).