From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw127729 [PATCH] drivers: fix vmxnet3 return wrong error c
Date: Tue, 30 May 2023 13:20:20 -0700 (PDT) [thread overview]
Message-ID: <64765a84.0d0a0220.e4045.36ddSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/127729
_Testing PASS_
Submitter: root <corezeng@gmail.com>
Date: Sunday, May 28 2023 14:37:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c9df59bcc9bec67783de98486879594e52bdc418
127729 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
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
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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 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
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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/26454/
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-30 20:20 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 20:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 23:03 dpdklab
2023-06-09 23:02 dpdklab
2023-06-09 22:58 dpdklab
2023-06-08 22:31 dpdklab
2023-06-08 22:31 dpdklab
2023-06-08 22:31 dpdklab
2023-06-08 22:31 dpdklab
2023-06-08 22:29 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-06-08 22:27 dpdklab
2023-05-30 23:24 dpdklab
2023-05-30 23:16 dpdklab
2023-05-30 23:14 dpdklab
2023-05-30 23:09 dpdklab
2023-05-30 23:05 dpdklab
2023-05-30 22:49 dpdklab
2023-05-30 20:20 dpdklab
2023-05-30 20:20 dpdklab
2023-05-30 20:20 dpdklab
2023-05-30 20:03 dpdklab
2023-05-30 20:01 dpdklab
2023-05-30 20:01 dpdklab
2023-05-30 20:00 dpdklab
2023-05-30 19:55 dpdklab
2023-05-30 19:48 dpdklab
2023-05-30 19:40 dpdklab
2023-05-30 19:38 dpdklab
2023-05-30 19:34 dpdklab
2023-05-30 19:25 dpdklab
2023-05-30 19:25 dpdklab
2023-05-30 19:24 dpdklab
2023-05-30 19:20 dpdklab
2023-05-30 19:18 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=64765a84.0d0a0220.e4045.36ddSMTPIN_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).