From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134908-134909 [PATCH] [v2,2/2] common/idpf: enable AVX2
Date: Thu, 07 Dec 2023 03:26:25 -0800 (PST) [thread overview]
Message-ID: <6571abe1.4a0a0220.d2502.2cd6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134909
_Testing PASS_
Submitter: Wenzhuo Lu <wenzhuo.lu@intel.com>
Date: Thursday, December 07 2023 07:46:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
134908-134909 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
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/28549/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-07 11:26 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 11:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 4:01 dpdklab
2023-12-07 13:04 dpdklab
2023-12-07 12:45 dpdklab
2023-12-07 12:14 dpdklab
2023-12-07 12:13 dpdklab
2023-12-07 12:08 dpdklab
2023-12-07 12:02 dpdklab
2023-12-07 12:02 dpdklab
2023-12-07 12:02 dpdklab
2023-12-07 12:02 dpdklab
2023-12-07 12:01 dpdklab
2023-12-07 12:01 dpdklab
2023-12-07 12:00 dpdklab
2023-12-07 11:39 dpdklab
2023-12-07 11:38 dpdklab
2023-12-07 11:38 dpdklab
2023-12-07 11:38 dpdklab
2023-12-07 11:37 dpdklab
2023-12-07 11:37 dpdklab
2023-12-07 11:37 dpdklab
2023-12-07 11:37 dpdklab
2023-12-07 11:36 dpdklab
2023-12-07 11:36 dpdklab
2023-12-07 11:35 dpdklab
2023-12-07 11:25 dpdklab
2023-12-07 11:25 dpdklab
2023-12-07 11:23 dpdklab
2023-12-07 11:22 dpdklab
2023-12-07 11:22 dpdklab
2023-12-07 11:22 dpdklab
2023-12-07 11:21 dpdklab
2023-12-07 11:20 dpdklab
2023-12-07 11:19 dpdklab
2023-12-07 11:19 dpdklab
2023-12-07 11:18 dpdklab
2023-12-07 11:17 dpdklab
2023-12-07 11:16 dpdklab
2023-12-07 11:15 dpdklab
2023-12-07 11:15 dpdklab
2023-12-07 11:10 dpdklab
2023-12-07 11:09 dpdklab
2023-12-07 11:06 dpdklab
2023-12-07 11:01 dpdklab
2023-12-07 11:01 dpdklab
2023-12-07 10:59 dpdklab
2023-12-07 10:59 dpdklab
2023-12-07 10:59 dpdklab
2023-12-07 10:50 dpdklab
2023-12-07 10:50 dpdklab
2023-12-07 10:50 dpdklab
2023-12-07 10:49 dpdklab
2023-12-07 10:49 dpdklab
2023-12-07 10:49 dpdklab
2023-12-07 10:45 dpdklab
2023-12-07 10:45 dpdklab
2023-12-07 10:38 dpdklab
2023-12-07 10:36 dpdklab
2023-12-07 10:36 dpdklab
2023-12-07 10:35 dpdklab
2023-12-07 10:34 dpdklab
2023-12-07 10:33 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=6571abe1.4a0a0220.d2502.2cd6SMTPIN_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).