automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw144117-144121 [PATCH] [v4,5/5] app/test: add unit tests
Date: Tue, 17 Sep 2024 16:30:44 -0700 (PDT)	[thread overview]
Message-ID: <66ea1124.050a0220.207fce.177eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240917120946.1212-6-konstantin.v.ananyev@yandex.ru>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/144121

_Testing PASS_

Submitter: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Date: Tuesday, September 17 2024 12:09:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144117-144121 --> testing pass

Upstream job id: Windows-Compile-DPDK-Native#22290

Test environment and result as below:

+---------------------+-----------------------+----------------------+--------------------+
|     Environment     | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_meson_compile |
+=====================+=======================+======================+====================+
| Windows Server 2022 | PASS                  | PASS                 | SKIPPED            |
+---------------------+-----------------------+----------------------+--------------------+
| FreeBSD 13.3        | SKIPPED               | SKIPPED              | PASS               |
+---------------------+-----------------------+----------------------+--------------------+
| FreeBSD 14.1        | SKIPPED               | SKIPPED              | PASS               |
+---------------------+-----------------------+----------------------+--------------------+


Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p5
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31047/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-09-17 23:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240917120946.1212-6-konstantin.v.ananyev@yandex.ru>
2024-09-17 11:44 ` |SUCCESS| pw144117-144121 [PATCH v4 5/5] app/test: add unit tests for soring API qemudev
2024-09-17 11:49 ` qemudev
2024-09-17 12:12 ` |WARNING| pw144121 " checkpatch
2024-09-17 13:04 ` |SUCCESS| " 0-day Robot
2024-09-17 19:36 ` |SUCCESS| pw144117-144121 [PATCH] [v4,5/5] app/test: add unit tests dpdklab
2024-09-17 20:58 ` dpdklab
2024-09-17 21:18 ` dpdklab
2024-09-17 21:27 ` dpdklab
2024-09-17 22:03 ` dpdklab
2024-09-17 23:16 ` |PENDING| " dpdklab
2024-09-17 23:27 ` dpdklab
2024-09-17 23:30 ` dpdklab [this message]
2024-09-17 23:52 ` dpdklab
2024-09-17 23:57 ` dpdklab
2024-09-18  0:44 ` |SUCCESS| " dpdklab
2024-09-18  1:00 ` dpdklab
2024-09-18  1:14 ` |WARNING| " dpdklab
2024-09-18  2:47 ` |SUCCESS| " dpdklab
2024-09-18  4:11 ` dpdklab
2024-09-18  4:59 ` dpdklab
2024-09-18  5:21 ` dpdklab
2024-09-18  9:39 ` dpdklab
2024-09-22  8:16 ` dpdklab
2024-09-22  8:29 ` 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=66ea1124.050a0220.207fce.177eSMTPIN_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).