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| pw126508-126511 [PATCH] [v2, 4/4] app: add testgraph application
Date: Tue, 25 Apr 2023 11:59:04 -0700 (PDT) [thread overview]
Message-ID: <644822f8.050a0220.c264f.70d2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126511
_Testing PASS_
Submitter: Vamsi Attunuru <vattunuru@marvell.com>
Date: Tuesday, April 25 2023 13:15:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70cc4e1fed665712e68f2f45d98dda4abc6accda
126508-126511 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| RHEL 7 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| CentOS Stream 9 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
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)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26117/
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-25 18:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 18:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-25 19:02 dpdklab
2023-04-25 18:40 dpdklab
2023-04-25 18:37 dpdklab
2023-04-25 18:11 dpdklab
2023-04-25 18:06 dpdklab
2023-04-25 18:02 dpdklab
2023-04-25 18:02 dpdklab
2023-04-25 17:22 dpdklab
2023-04-25 17:21 dpdklab
2023-04-25 15:17 dpdklab
2023-04-25 15:16 dpdklab
2023-04-25 15:07 dpdklab
2023-04-25 14:44 dpdklab
2023-04-25 14:44 dpdklab
2023-04-25 14:40 dpdklab
2023-04-25 14:39 dpdklab
2023-04-25 14:38 dpdklab
2023-04-25 14:37 dpdklab
2023-04-25 14:37 dpdklab
2023-04-25 14:37 dpdklab
2023-04-25 14:31 dpdklab
2023-04-25 14:28 dpdklab
2023-04-25 14:20 dpdklab
2023-04-25 14:19 dpdklab
2023-04-25 14:16 dpdklab
2023-04-25 14:16 dpdklab
2023-04-25 14:16 dpdklab
2023-04-25 14:13 dpdklab
2023-04-25 14:09 dpdklab
2023-04-25 14:08 dpdklab
2023-04-25 14:03 dpdklab
2023-04-25 14:02 dpdklab
2023-04-25 14:00 dpdklab
[not found] <20230425131516.3308612-5-vattunuru@marvell.com>
2023-04-25 13:05 ` |SUCCESS| pw126508-126511 [PATCH v2 " qemudev
2023-04-25 13:09 ` qemudev
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=644822f8.050a0220.c264f.70d2SMTPIN_ADDED_MISSING@mx.google.com \
--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).