From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132298 [PATCH] [v3] net/axgbe: use CPUID to identify cpu
Date: Wed, 04 Oct 2023 07:10:15 -0700 (PDT) [thread overview]
Message-ID: <651d7247.920a0220.81511.9595SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132298
_Testing PASS_
Submitter: Selwin Sebastian <selwin.sebastian@amd.com>
Date: Wednesday, October 04 2023 10:07:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:687a5b12b14f02f0d3624f4b36b34dba8119a680
132298 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | SKIPPED | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27821/
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-04 14:10 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 14:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-04 16:24 dpdklab
2023-10-04 16:18 dpdklab
2023-10-04 16:10 dpdklab
2023-10-04 16:01 dpdklab
2023-10-04 15:41 dpdklab
2023-10-04 15:38 dpdklab
2023-10-04 15:35 dpdklab
2023-10-04 15:33 dpdklab
2023-10-04 15:30 dpdklab
2023-10-04 15:30 dpdklab
2023-10-04 15:26 dpdklab
2023-10-04 15:22 dpdklab
2023-10-04 15:19 dpdklab
2023-10-04 15:19 dpdklab
2023-10-04 15:16 dpdklab
2023-10-04 15:15 dpdklab
2023-10-04 15:11 dpdklab
2023-10-04 14:50 dpdklab
2023-10-04 14:49 dpdklab
2023-10-04 14:47 dpdklab
2023-10-04 14:44 dpdklab
2023-10-04 14:44 dpdklab
2023-10-04 14:44 dpdklab
2023-10-04 14:43 dpdklab
2023-10-04 14:41 dpdklab
2023-10-04 14:40 dpdklab
2023-10-04 14:39 dpdklab
2023-10-04 14:38 dpdklab
2023-10-04 14:36 dpdklab
2023-10-04 14:32 dpdklab
2023-10-04 14:29 dpdklab
2023-10-04 14:29 dpdklab
2023-10-04 14:28 dpdklab
2023-10-04 14:19 dpdklab
2023-10-04 14:13 dpdklab
2023-10-04 14:12 dpdklab
2023-10-04 14:08 dpdklab
2023-10-04 14:08 dpdklab
2023-10-04 14:08 dpdklab
2023-10-04 14:08 dpdklab
2023-10-04 14:08 dpdklab
2023-10-04 14:06 dpdklab
2023-10-04 14:06 dpdklab
2023-10-04 14:04 dpdklab
2023-10-04 14:03 dpdklab
2023-10-04 14:00 dpdklab
2023-10-04 13:59 dpdklab
2023-10-04 13:56 dpdklab
[not found] <20231004100754.111493-1-selwin.sebastian@amd.com>
2023-10-04 9:49 ` |SUCCESS| pw132298 [PATCH v3] " qemudev
2023-10-04 9:53 ` qemudev
2023-10-04 10: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=651d7247.920a0220.81511.9595SMTPIN_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).