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| pw143753-143756 [PATCH] [RFC,4/4] test/thash: add tests fo
Date: Tue, 10 Sep 2024 01:33:56 -0700 (PDT)	[thread overview]
Message-ID: <66e00474.170a0220.13c80c.db95SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906165318.1322550-5-vladimir.medvedkin@intel.com>

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

_Testing PASS_

Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Friday, September 06 2024 16:53:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143753-143756 --> testing pass

Upstream job id: Generic-VM-DPDK-Compile-Meson#29310

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/30947/

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-10  8:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906165318.1322550-5-vladimir.medvedkin@intel.com>
2024-09-06 16:27 ` |SUCCESS| pw143753-143756 [RFC 4/4] test/thash: add tests for RSS key generation API qemudev
2024-09-06 16:31 ` qemudev
2024-09-06 16:55 ` |SUCCESS| pw143756 " checkpatch
2024-09-06 17:44 ` 0-day Robot
2024-09-10  4:45 ` |SUCCESS| pw143753-143756 [PATCH] [RFC,4/4] test/thash: add tests fo dpdklab
2024-09-10  4:54 ` dpdklab
2024-09-10  5:38 ` dpdklab
2024-09-10  8:33 ` dpdklab
2024-09-10  8:33 ` dpdklab [this message]
2024-09-10  8:44 ` |PENDING| " dpdklab
2024-09-10  9:18 ` dpdklab
2024-09-10  9:20 ` |SUCCESS| " dpdklab
2024-09-10 11:02 ` |PENDING| " dpdklab
2024-09-10 11:13 ` |SUCCESS| " dpdklab
2024-09-10 11:40 ` dpdklab
2024-09-10 11:53 ` dpdklab
2024-09-10 12:36 ` dpdklab
2024-09-10 12:46 ` dpdklab
2024-09-10 12:47 ` dpdklab
2024-09-10 15:14 ` dpdklab
2024-09-10 15:18 ` dpdklab
2024-09-10 15:22 ` dpdklab
2024-09-10 15:26 ` dpdklab
2024-09-10 15:45 ` dpdklab
2024-09-16  4:09 ` dpdklab
2024-09-16 10:08 ` 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=66e00474.170a0220.13c80c.db95SMTPIN_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).