From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129716 [PATCH] [v4] node: add IPv4 reassembly node
Date: Thu, 27 Jul 2023 08:30:15 -0700 (PDT) [thread overview]
Message-ID: <64c28d87.4a0a0220.43f20.5bfdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129716
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thursday, July 27 2023 14:36:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d01be82476a1d3c7b4ffc24cd5286ca10844e6b2
129716 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
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
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
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/27150/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-27 15:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 15:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-27 18:28 dpdklab
2023-07-27 16:25 dpdklab
2023-07-27 16:15 dpdklab
2023-07-27 16:14 dpdklab
2023-07-27 16:10 dpdklab
2023-07-27 15:54 dpdklab
2023-07-27 15:53 dpdklab
2023-07-27 15:51 dpdklab
2023-07-27 15:48 dpdklab
2023-07-27 15:43 dpdklab
2023-07-27 15:40 dpdklab
2023-07-27 15:36 dpdklab
2023-07-27 15:28 dpdklab
2023-07-27 15:27 dpdklab
2023-07-27 15:27 dpdklab
2023-07-27 15:26 dpdklab
2023-07-27 15:26 dpdklab
2023-07-27 15:21 dpdklab
2023-07-27 15:17 dpdklab
2023-07-27 15:15 dpdklab
2023-07-27 15:14 dpdklab
2023-07-27 15:14 dpdklab
2023-07-27 15:14 dpdklab
2023-07-27 15:14 dpdklab
2023-07-27 15:14 dpdklab
2023-07-27 15:13 dpdklab
2023-07-27 15:13 dpdklab
2023-07-27 15:13 dpdklab
[not found] <20230727143656.10260-1-pbhagavatula@marvell.com>
2023-07-27 14:24 ` |SUCCESS| pw129716 [PATCH v4] " qemudev
2023-07-27 14:28 ` qemudev
2023-07-27 14:37 ` checkpatch
2023-07-27 15:38 ` 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=64c28d87.4a0a0220.43f20.5bfdSMTPIN_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).