From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130449-130458 [PATCH] [v5,10/10] test: remove double reg
Date: Thu, 17 Aug 2023 00:49:44 -0700 (PDT) [thread overview]
Message-ID: <64ddd118.250a0220.1bbfe.9638SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130458
_Testing PASS_
Submitter: Sinan Kaya <okaya@kernel.org>
Date: Thursday, August 17 2023 04:30:27
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130449-130458 --> testing pass
Test environment and result as below:
+---------------------+----------------------+--------------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile |
+=====================+======================+====================+
| Windows Server 2019 | PASS | PASS |
+---------------------+----------------------+--------------------+
| FreeBSD 13 | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
| Debian Buster | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
| CentOS Stream 8 | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
| CentOS Stream 9 | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
| Debian Bullseye | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
| Fedora 38 | SKIPPED | PASS |
+---------------------+----------------------+--------------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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
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
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27363/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-17 7:49 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 7:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 9:11 dpdklab
2023-08-18 9:06 dpdklab
2023-08-18 9:01 dpdklab
2023-08-18 8:57 dpdklab
2023-08-18 8:41 dpdklab
2023-08-18 0:00 dpdklab
2023-08-17 9:22 dpdklab
2023-08-17 9:18 dpdklab
2023-08-17 8:55 dpdklab
2023-08-17 8:54 dpdklab
2023-08-17 8:50 dpdklab
2023-08-17 8:46 dpdklab
2023-08-17 8:46 dpdklab
2023-08-17 8:37 dpdklab
2023-08-17 8:30 dpdklab
2023-08-17 8:30 dpdklab
2023-08-17 8:29 dpdklab
2023-08-17 8:24 dpdklab
2023-08-17 8:23 dpdklab
2023-08-17 8:15 dpdklab
2023-08-17 8:13 dpdklab
2023-08-17 8:13 dpdklab
2023-08-17 8:11 dpdklab
2023-08-17 8:11 dpdklab
2023-08-17 8:11 dpdklab
2023-08-17 8:11 dpdklab
2023-08-17 8:10 dpdklab
2023-08-17 8:08 dpdklab
2023-08-17 8:06 dpdklab
2023-08-17 8:03 dpdklab
2023-08-17 7:58 dpdklab
2023-08-17 7:49 dpdklab
2023-08-17 7:45 dpdklab
2023-08-17 7:44 dpdklab
2023-08-17 7:44 dpdklab
2023-08-17 7:40 dpdklab
2023-08-17 7:39 dpdklab
2023-08-17 7:37 dpdklab
2023-08-17 7:35 dpdklab
2023-08-17 7:34 dpdklab
2023-08-17 7:34 dpdklab
2023-08-17 7:13 dpdklab
2023-08-17 7:08 dpdklab
2023-08-17 6:40 dpdklab
2023-08-17 6:40 dpdklab
2023-08-17 6:10 dpdklab
2023-08-17 6:09 dpdklab
2023-08-17 6:08 dpdklab
2023-08-17 6:05 dpdklab
2023-08-17 6:02 dpdklab
2023-08-17 6:00 dpdklab
2023-08-17 5:58 dpdklab
2023-08-17 5:56 dpdklab
2023-08-17 5:55 dpdklab
2023-08-17 5:51 dpdklab
2023-08-17 5:47 dpdklab
2023-08-17 5:45 dpdklab
2023-08-17 5:44 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=64ddd118.250a0220.1bbfe.9638SMTPIN_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).