From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: |SUCCESS| pw128997 [PATCH] [v4] app/testpmd: add trace dump command
Date: Mon, 26 Jun 2023 07:55:55 -0700 (PDT) [thread overview]
Message-ID: <6499a6fb.050a0220.4ad6c.84acSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128997
_Testing PASS_
Submitter: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Date: Monday, June 26 2023 11:57:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6c948396d7ebc7c0ffdac7df99f1ebf7b4ecb55f
128997 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| CentOS Stream 9 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| Fedora 37 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| Fedora 38 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
| Debian Bullseye | PASS |
+------------------+----------+
| RHEL 7 | PASS |
+------------------+----------+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| Debian Buster | PASS |
+------------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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)
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26812/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-26 14:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 14:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-26 18:53 dpdklab
2023-06-26 18:37 dpdklab
2023-06-26 18:11 dpdklab
2023-06-26 17:59 dpdklab
2023-06-26 17:54 dpdklab
2023-06-26 17:34 dpdklab
2023-06-26 17:32 dpdklab
2023-06-26 17:12 dpdklab
2023-06-26 16:27 dpdklab
2023-06-26 16:17 dpdklab
2023-06-26 15:30 dpdklab
2023-06-26 14:59 dpdklab
2023-06-26 14:56 dpdklab
2023-06-26 14:56 dpdklab
2023-06-26 14:54 dpdklab
2023-06-26 14:47 dpdklab
2023-06-26 14:45 dpdklab
2023-06-26 14:44 dpdklab
2023-06-26 14:43 dpdklab
2023-06-26 14:33 dpdklab
2023-06-26 14:26 dpdklab
2023-06-26 14:20 dpdklab
2023-06-26 14:07 dpdklab
2023-06-26 14:06 dpdklab
2023-06-26 13:58 dpdklab
2023-06-26 13:37 dpdklab
2023-06-26 13:31 dpdklab
2023-06-26 13:26 dpdklab
2023-06-26 13:26 dpdklab
2023-06-26 13:25 dpdklab
[not found] <20230626115749.8961-1-viacheslavo@nvidia.com>
2023-06-26 11:47 ` |SUCCESS| pw128997 [PATCH v4] " qemudev
2023-06-26 11:51 ` qemudev
2023-06-26 12:59 ` 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=6499a6fb.050a0220.4ad6c.84acSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=viacheslavo@nvidia.com \
/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).