From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info i
Date: Thu, 14 Mar 2024 10:30:43 -0700 (PDT) [thread overview]
Message-ID: <65f33443.170a0220.dc15d.2b19SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240314162819.16971-1-stephen@networkplumber.org>
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138406
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, March 14 2024 16:28:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cd218549b686d6be394ef3b171eafa16c038bfe3
138406 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Fedora 38 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Debian 12 (arm) | PASS |
+------------------+----------+
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
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
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29561/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-14 17:30 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240314162819.16971-1-stephen@networkplumber.org>
2024-03-14 16:16 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info in version.map qemudev
2024-03-14 16:21 ` qemudev
2024-03-14 16:28 ` checkpatch
2024-03-14 17:11 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info i dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:12 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:13 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:14 ` dpdklab
2024-03-14 17:15 ` dpdklab
2024-03-14 17:16 ` dpdklab
2024-03-14 17:19 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:20 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:21 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:22 ` dpdklab
2024-03-14 17:23 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info in version.map 0-day Robot
2024-03-14 17:24 ` |SUCCESS| pw138406 [PATCH] eal: fix comment about vfio device info i dpdklab
2024-03-14 17:24 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:25 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:26 ` dpdklab
2024-03-14 17:27 ` dpdklab
2024-03-14 17:27 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:28 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:29 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab [this message]
2024-03-14 17:30 ` dpdklab
2024-03-14 17:30 ` dpdklab
2024-03-14 17:32 ` dpdklab
2024-03-14 17:33 ` dpdklab
2024-03-14 17:33 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:36 ` dpdklab
2024-03-14 17:56 ` dpdklab
2024-03-14 18:30 ` dpdklab
2024-03-14 18:37 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:51 ` 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=65f33443.170a0220.dc15d.2b19SMTPIN_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).