From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133727-133726 [PATCH] [v4,4/4] test: add unit test for p
Date: Wed, 01 Nov 2023 06:32:11 -0700 (PDT) [thread overview]
Message-ID: <6542535b.0c0a0220.7cff8.b111SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133726
_Testing PASS_
Submitter: Paul Szczepanek <paul.szczepanek@arm.com>
Date: Wednesday, November 01 2023 12:46:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:1025bd1c24b1be70e028c7ba0595782bce75fcc6
133727-133726 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28180/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-01 13:32 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 13:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-01 14:46 dpdklab
2023-11-01 14:45 dpdklab
2023-11-01 14:42 dpdklab
2023-11-01 14:42 dpdklab
2023-11-01 14:42 dpdklab
2023-11-01 14:42 dpdklab
2023-11-01 14:38 dpdklab
2023-11-01 14:31 dpdklab
2023-11-01 14:27 dpdklab
2023-11-01 14:27 dpdklab
2023-11-01 14:27 dpdklab
2023-11-01 14:25 dpdklab
2023-11-01 13:58 dpdklab
2023-11-01 13:58 dpdklab
2023-11-01 13:58 dpdklab
2023-11-01 13:54 dpdklab
2023-11-01 13:54 dpdklab
2023-11-01 13:53 dpdklab
2023-11-01 13:53 dpdklab
2023-11-01 13:53 dpdklab
2023-11-01 13:53 dpdklab
2023-11-01 13:52 dpdklab
2023-11-01 13:52 dpdklab
2023-11-01 13:52 dpdklab
2023-11-01 13:52 dpdklab
2023-11-01 13:51 dpdklab
2023-11-01 13:51 dpdklab
2023-11-01 13:51 dpdklab
2023-11-01 13:42 dpdklab
2023-11-01 13:41 dpdklab
2023-11-01 13:41 dpdklab
2023-11-01 13:40 dpdklab
2023-11-01 13:40 dpdklab
2023-11-01 13:40 dpdklab
2023-11-01 13:38 dpdklab
2023-11-01 13:38 dpdklab
2023-11-01 13:38 dpdklab
2023-11-01 13:36 dpdklab
2023-11-01 13:35 dpdklab
2023-11-01 13:34 dpdklab
2023-11-01 13:33 dpdklab
2023-11-01 13:33 dpdklab
2023-11-01 13:33 dpdklab
2023-11-01 13:32 dpdklab
2023-11-01 13:32 dpdklab
2023-11-01 13:32 dpdklab
2023-11-01 13:32 dpdklab
2023-11-01 13:32 dpdklab
2023-11-01 13:31 dpdklab
2023-11-01 13:30 dpdklab
2023-11-01 13:30 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=6542535b.0c0a0220.7cff8.b111SMTPIN_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).