From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125971 [PATCH] eventdev/timer: move buffer flush call
Date: Thu, 13 Apr 2023 00:34:47 +0000 (UTC) [thread overview]
Message-ID: <20230413003447.96ABF60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125971
_Testing PASS_
Submitter: Carrillo, Erik G <erik.g.carrillo@intel.com>
Date: Wednesday, April 12 2023 19:56:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
125971 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25975/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-13 0:34 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 0:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-13 5:26 dpdklab
2023-04-13 5:26 dpdklab
2023-04-13 4:16 dpdklab
2023-04-13 4:16 dpdklab
2023-04-13 2:30 dpdklab
2023-04-13 2:26 dpdklab
2023-04-13 2:10 dpdklab
2023-04-13 2:06 dpdklab
2023-04-13 2:01 dpdklab
2023-04-13 1:56 dpdklab
2023-04-13 1:37 dpdklab
2023-04-13 1:37 dpdklab
2023-04-13 1:31 dpdklab
2023-04-13 1:28 dpdklab
2023-04-13 1:25 dpdklab
2023-04-13 1:22 dpdklab
2023-04-13 1:22 dpdklab
2023-04-13 1:21 dpdklab
2023-04-13 1:13 dpdklab
2023-04-13 1:12 dpdklab
2023-04-13 1:10 dpdklab
2023-04-13 1:05 dpdklab
2023-04-13 1:04 dpdklab
2023-04-13 1:02 dpdklab
2023-04-13 0:59 dpdklab
2023-04-13 0:57 dpdklab
2023-04-13 0:55 dpdklab
2023-04-13 0:50 dpdklab
2023-04-13 0:31 dpdklab
2023-04-13 0:28 dpdklab
2023-04-13 0:25 dpdklab
2023-04-13 0:01 dpdklab
2023-04-12 23:26 dpdklab
2023-04-12 23:13 dpdklab
2023-04-12 23:13 dpdklab
2023-04-12 23:00 dpdklab
2023-04-12 22:53 dpdklab
2023-04-12 22:51 dpdklab
2023-04-12 22:44 dpdklab
2023-04-12 22:43 dpdklab
2023-04-12 22:40 dpdklab
2023-04-12 22:34 dpdklab
2023-04-12 22:30 dpdklab
2023-04-12 22:30 dpdklab
2023-04-12 22:28 dpdklab
2023-04-12 22:27 dpdklab
2023-04-12 22:20 dpdklab
2023-04-12 22:19 dpdklab
2023-04-12 22:18 dpdklab
2023-04-12 22:17 dpdklab
2023-04-12 22:17 dpdklab
2023-04-12 22:10 dpdklab
[not found] <20230412195637.450033-1-erik.g.carrillo@intel.com>
2023-04-12 19:47 ` qemudev
2023-04-12 19:51 ` qemudev
2023-04-12 21:18 ` 0-day Robot
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=20230413003447.96ABF60095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).