From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132461 [PATCH] eventdev: fix symbol export for port main
Date: Tue, 10 Oct 2023 08:32:06 -0700 (PDT) [thread overview]
Message-ID: <65256e76.4a0a0220.d4638.cdb6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132461
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, October 10 2023 14:00:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4dd146e597d81d900140a904e0b3b9feb1b0be6c
132461 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27880/
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-10 15:32 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-12 11:25 dpdklab
2023-10-11 21:53 dpdklab
2023-10-11 21:47 dpdklab
2023-10-11 21:43 dpdklab
2023-10-10 18:53 dpdklab
2023-10-10 18:39 dpdklab
2023-10-10 17:09 dpdklab
2023-10-10 17:01 dpdklab
2023-10-10 17:01 dpdklab
2023-10-10 16:58 dpdklab
2023-10-10 16:58 dpdklab
2023-10-10 16:55 dpdklab
2023-10-10 16:52 dpdklab
2023-10-10 16:44 dpdklab
2023-10-10 16:44 dpdklab
2023-10-10 16:43 dpdklab
2023-10-10 16:43 dpdklab
2023-10-10 16:42 dpdklab
2023-10-10 16:34 dpdklab
2023-10-10 16:18 dpdklab
2023-10-10 16:04 dpdklab
2023-10-10 15:58 dpdklab
2023-10-10 15:58 dpdklab
2023-10-10 15:58 dpdklab
2023-10-10 15:51 dpdklab
2023-10-10 15:49 dpdklab
2023-10-10 15:49 dpdklab
2023-10-10 15:46 dpdklab
2023-10-10 15:45 dpdklab
2023-10-10 15:44 dpdklab
2023-10-10 15:42 dpdklab
2023-10-10 15:42 dpdklab
2023-10-10 15:41 dpdklab
2023-10-10 15:39 dpdklab
2023-10-10 15:31 dpdklab
2023-10-10 15:31 dpdklab
2023-10-10 15:31 dpdklab
2023-10-10 15:29 dpdklab
2023-10-10 15:28 dpdklab
2023-10-10 15:27 dpdklab
2023-10-10 15:27 dpdklab
2023-10-10 15:26 dpdklab
2023-10-10 15:25 dpdklab
2023-10-10 15:24 dpdklab
2023-10-10 15:22 dpdklab
2023-10-10 15:20 dpdklab
2023-10-10 15:06 dpdklab
2023-10-10 15:05 dpdklab
2023-10-10 15:04 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=65256e76.4a0a0220.d4638.cdb6SMTPIN_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).