From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132618-132620 [PATCH] [3/3] common/cnxk: check for error
Date: Mon, 16 Oct 2023 04:15:44 -0700 (PDT) [thread overview]
Message-ID: <652d1b60.170a0220.e324a.d974SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132620
_Testing PASS_
Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Monday, October 16 2023 07:04:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:441e777b85f1ea1eb6a2a970ff5d5c8e027f520c
132618-132620 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27935/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-16 11:15 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 11:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 21:08 dpdklab
2023-10-16 19:11 dpdklab
2023-10-16 18:59 dpdklab
2023-10-16 12:56 dpdklab
2023-10-16 12:08 dpdklab
2023-10-16 11:58 dpdklab
2023-10-16 11:57 dpdklab
2023-10-16 11:49 dpdklab
2023-10-16 11:48 dpdklab
2023-10-16 11:28 dpdklab
2023-10-16 11:23 dpdklab
2023-10-16 11:21 dpdklab
2023-10-16 11:21 dpdklab
2023-10-16 11:17 dpdklab
2023-10-16 11:17 dpdklab
2023-10-16 11:16 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:14 dpdklab
2023-10-16 11:14 dpdklab
2023-10-16 11:14 dpdklab
2023-10-16 11:14 dpdklab
2023-10-16 11:12 dpdklab
2023-10-16 11:12 dpdklab
2023-10-16 11:12 dpdklab
2023-10-16 11:08 dpdklab
2023-10-16 11:07 dpdklab
2023-10-16 11:07 dpdklab
2023-10-16 11:06 dpdklab
2023-10-16 11:06 dpdklab
2023-10-16 11:05 dpdklab
2023-10-16 11:04 dpdklab
2023-10-16 11:04 dpdklab
2023-10-16 11:01 dpdklab
2023-10-16 10:59 dpdklab
2023-10-16 10:58 dpdklab
2023-10-16 10:58 dpdklab
2023-10-16 10:57 dpdklab
2023-10-16 10:57 dpdklab
2023-10-16 10:56 dpdklab
2023-10-16 10:56 dpdklab
2023-10-16 10:55 dpdklab
2023-10-16 10:52 dpdklab
2023-10-16 10:48 dpdklab
2023-10-16 10:46 dpdklab
2023-10-16 10:44 dpdklab
2023-10-16 10:44 dpdklab
2023-10-16 10:43 dpdklab
2023-10-16 10:06 dpdklab
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=652d1b60.170a0220.e324a.d974SMTPIN_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).