From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137879 [PATCH] [v2] vhost: fix VDUSE device destruction
Date: Mon, 04 Mar 2024 03:23:27 -0800 (PST) [thread overview]
Message-ID: <65e5af2f.170a0220.6e97f.0a51SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240304103558.1500695-1-david.marchand@redhat.com>
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137879
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Monday, March 04 2024 10:35:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137879 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| Debian Bullseye | PASS |
+-----------------+----------+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Ubuntu 22.04 | PASS |
+-----------------+----------+
| RHEL8 | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
| Fedora 37 | 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
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)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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/29401/
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-04 11:23 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240304103558.1500695-1-david.marchand@redhat.com>
2024-03-04 10:13 ` |SUCCESS| pw137879 [PATCH v2] vhost: fix VDUSE device destruction failure qemudev
2024-03-04 10:18 ` qemudev
2024-03-04 10:37 ` checkpatch
2024-03-04 11:14 ` |SUCCESS| pw137879 [PATCH] [v2] vhost: fix VDUSE device destruction dpdklab
2024-03-04 11:14 ` dpdklab
2024-03-04 11:15 ` dpdklab
2024-03-04 11:15 ` dpdklab
2024-03-04 11:15 ` dpdklab
2024-03-04 11:15 ` dpdklab
2024-03-04 11:16 ` dpdklab
2024-03-04 11:16 ` dpdklab
2024-03-04 11:16 ` dpdklab
2024-03-04 11:17 ` dpdklab
2024-03-04 11:17 ` dpdklab
2024-03-04 11:17 ` dpdklab
2024-03-04 11:17 ` dpdklab
2024-03-04 11:18 ` dpdklab
2024-03-04 11:18 ` dpdklab
2024-03-04 11:19 ` dpdklab
2024-03-04 11:19 ` dpdklab
2024-03-04 11:19 ` dpdklab
2024-03-04 11:19 ` dpdklab
2024-03-04 11:20 ` dpdklab
2024-03-04 11:20 ` dpdklab
2024-03-04 11:20 ` dpdklab
2024-03-04 11:20 ` dpdklab
2024-03-04 11:21 ` dpdklab
2024-03-04 11:21 ` dpdklab
2024-03-04 11:21 ` dpdklab
2024-03-04 11:21 ` dpdklab
2024-03-04 11:21 ` dpdklab
2024-03-04 11:22 ` dpdklab
2024-03-04 11:22 ` dpdklab
2024-03-04 11:22 ` dpdklab
2024-03-04 11:22 ` dpdklab
2024-03-04 11:22 ` dpdklab
2024-03-04 11:22 ` dpdklab
2024-03-04 11:23 ` dpdklab
2024-03-04 11:23 ` dpdklab [this message]
2024-03-04 11:23 ` dpdklab
2024-03-04 11:23 ` dpdklab
2024-03-04 11:24 ` dpdklab
2024-03-04 11:24 ` dpdklab
2024-03-04 11:24 ` dpdklab
2024-03-04 11:24 ` dpdklab
2024-03-04 11:24 ` dpdklab
2024-03-04 11:24 ` dpdklab
2024-03-04 11:25 ` dpdklab
2024-03-04 11:25 ` |SUCCESS| pw137879 [PATCH v2] vhost: fix VDUSE device destruction failure 0-day Robot
2024-03-04 11:25 ` |SUCCESS| pw137879 [PATCH] [v2] vhost: fix VDUSE device destruction dpdklab
2024-03-04 11:25 ` dpdklab
2024-03-04 11:25 ` dpdklab
2024-03-04 11:26 ` dpdklab
2024-03-04 11:26 ` dpdklab
2024-03-04 11:26 ` dpdklab
2024-03-04 11:28 ` dpdklab
2024-03-04 11:30 ` dpdklab
2024-03-04 11:31 ` dpdklab
2024-03-04 11:32 ` dpdklab
2024-03-04 11:32 ` dpdklab
2024-03-04 11:38 ` dpdklab
2024-03-04 11:41 ` dpdklab
2024-03-04 11:50 ` dpdklab
2024-03-04 11:50 ` dpdklab
2024-03-04 11:50 ` dpdklab
2024-03-04 11:51 ` dpdklab
2024-03-04 11:52 ` dpdklab
2024-03-04 11:58 ` dpdklab
2024-03-04 11:58 ` dpdklab
2024-03-04 12:23 ` dpdklab
2024-03-04 12:50 ` dpdklab
2024-03-07 21:21 ` dpdklab
2024-03-07 21:54 ` dpdklab
2024-03-07 22:26 ` 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=65e5af2f.170a0220.6e97f.0a51SMTPIN_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).