From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136056-136057 [PATCH] [v2,2/2] net/virtio-user: add VIRT
Date: Tue, 23 Jan 2024 03:52:03 -0800 (PST) [thread overview]
Message-ID: <65afa863.810a0220.3e397.c5bcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136057
_Testing PASS_
Submitter: Srujana Challa <schalla@marvell.com>
Date: Tuesday, January 23 2024 10:55:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:289ddcad152ebffa7359e414526707eb3f2c0a4a
136056-136057 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
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 Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28936/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-23 11:52 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 11:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-24 1:22 dpdklab
2024-01-24 1:03 dpdklab
2024-01-23 14:20 dpdklab
2024-01-23 12:47 dpdklab
2024-01-23 12:29 dpdklab
2024-01-23 12:28 dpdklab
2024-01-23 12:26 dpdklab
2024-01-23 12:25 dpdklab
2024-01-23 12:24 dpdklab
2024-01-23 12:22 dpdklab
2024-01-23 12:22 dpdklab
2024-01-23 12:21 dpdklab
2024-01-23 12:20 dpdklab
2024-01-23 12:19 dpdklab
2024-01-23 12:17 dpdklab
2024-01-23 12:17 dpdklab
2024-01-23 12:14 dpdklab
2024-01-23 12:13 dpdklab
2024-01-23 12:13 dpdklab
2024-01-23 12:11 dpdklab
2024-01-23 12:10 dpdklab
2024-01-23 12:10 dpdklab
2024-01-23 12:10 dpdklab
2024-01-23 12:02 dpdklab
2024-01-23 12:02 dpdklab
2024-01-23 12:01 dpdklab
2024-01-23 12:00 dpdklab
2024-01-23 11:57 dpdklab
2024-01-23 11:55 dpdklab
2024-01-23 11:52 dpdklab
2024-01-23 11:51 dpdklab
2024-01-23 11:51 dpdklab
2024-01-23 11:50 dpdklab
2024-01-23 11:50 dpdklab
2024-01-23 11:50 dpdklab
2024-01-23 11:49 dpdklab
2024-01-23 11:49 dpdklab
2024-01-23 11:48 dpdklab
2024-01-23 11:48 dpdklab
2024-01-23 11:47 dpdklab
2024-01-23 11:44 dpdklab
2024-01-23 11:44 dpdklab
2024-01-23 11:43 dpdklab
2024-01-23 11:42 dpdklab
2024-01-23 11:41 dpdklab
2024-01-23 11:41 dpdklab
2024-01-23 11:41 dpdklab
2024-01-23 11:41 dpdklab
2024-01-23 11:40 dpdklab
2024-01-23 11:39 dpdklab
2024-01-23 11:39 dpdklab
2024-01-23 11:39 dpdklab
2024-01-23 11:37 dpdklab
2024-01-23 11:36 dpdklab
2024-01-23 11:35 dpdklab
2024-01-23 11:35 dpdklab
2024-01-23 11:33 dpdklab
2024-01-23 11:32 dpdklab
2024-01-23 11:32 dpdklab
2024-01-23 11:32 dpdklab
2024-01-23 11:32 dpdklab
2024-01-23 11:32 dpdklab
2024-01-23 11:32 dpdklab
2024-01-23 11:32 dpdklab
2024-01-23 11:31 dpdklab
2024-01-23 11:31 dpdklab
2024-01-23 11:31 dpdklab
2024-01-23 11:30 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=65afa863.810a0220.3e397.c5bcSMTPIN_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).