From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125856 [PATCH] [v3] eventdev/eth_rx: fix invalid memory access
Date: Fri, 7 Apr 2023 18:42:26 +0000 (UTC) [thread overview]
Message-ID: <20230407184226.925B96012C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125856
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Friday, April 07 2023 06:47:32
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125856 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Ubuntu 22.04 | PASS |
+-----------------+----------+
| Debian Buster | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
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
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/25938/
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-07 18:42 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 18:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-07 20:37 dpdklab
2023-04-07 20:09 dpdklab
2023-04-07 19:56 dpdklab
2023-04-07 19:55 dpdklab
2023-04-07 19:49 dpdklab
2023-04-07 19:47 dpdklab
2023-04-07 19:42 dpdklab
2023-04-07 19:39 dpdklab
2023-04-07 19:30 dpdklab
2023-04-07 19:28 dpdklab
2023-04-07 19:25 dpdklab
2023-04-07 19:20 dpdklab
2023-04-07 19:16 dpdklab
2023-04-07 19:12 dpdklab
2023-04-07 19:09 dpdklab
2023-04-07 19:05 dpdklab
2023-04-07 19:02 dpdklab
2023-04-07 18:46 dpdklab
2023-04-07 18:46 dpdklab
2023-04-07 18:37 dpdklab
2023-04-07 18:35 dpdklab
2023-04-07 18:29 dpdklab
2023-04-07 18:25 dpdklab
2023-04-07 18:20 dpdklab
2023-04-07 18:18 dpdklab
2023-04-07 18:15 dpdklab
2023-04-07 18:13 dpdklab
2023-04-07 18:12 dpdklab
2023-04-07 18:11 dpdklab
2023-04-07 18:10 dpdklab
2023-04-07 18:09 dpdklab
2023-04-07 18:08 dpdklab
2023-04-07 18:03 dpdklab
2023-04-07 17:35 dpdklab
2023-04-07 17:32 dpdklab
2023-04-07 17:27 dpdklab
2023-04-07 17:23 dpdklab
2023-04-07 17:22 dpdklab
2023-04-07 17:20 dpdklab
2023-04-07 17:19 dpdklab
2023-04-07 17:17 dpdklab
2023-04-07 17:17 dpdklab
2023-04-07 17:15 dpdklab
2023-04-07 17:15 dpdklab
2023-04-07 17:14 dpdklab
2023-04-07 17:10 dpdklab
[not found] <20230407064732.891-1-pbhagavatula@marvell.com>
2023-04-07 6:37 ` |SUCCESS| pw125856 [PATCH v3] " qemudev
2023-04-07 6:41 ` qemudev
2023-04-07 6:49 ` checkpatch
2023-04-07 7:58 ` 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=20230407184226.925B96012C@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--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).