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| pw148424 [PATCH] [v2] dts: add time delay to async sniffer
Date: Sat, 16 Nov 2024 12:34:05 -0800 (PST)	[thread overview]
Message-ID: <673901bd.250a0220.2a7ff2.747fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241113185629.14327-1-npratte@iol.unh.edu>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/148424

_Testing PASS_

Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Wednesday, November 13 2024 18:56:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:78383e9816a8efe2ba16ec2ce65d51b94e6114e7

148424 --> testing pass

Upstream job id: Generic-VM-Unit-Test-DPDK#26265

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | 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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-11-16 20:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241113185629.14327-1-npratte@iol.unh.edu>
2024-11-13 18:30 ` |SUCCESS| pw148424 [PATCH v2] dts: add time delay to async sniffer callback function qemudev
2024-11-13 18:34 ` qemudev
2024-11-13 18:57 ` checkpatch
2024-11-13 19:45 ` 0-day Robot
2024-11-13 20:57 ` |SUCCESS| pw148424 [PATCH] [v2] dts: add time delay to async sniffer dpdklab
2024-11-13 21:03 ` dpdklab
2024-11-13 22:31 ` dpdklab
2024-11-13 22:32 ` dpdklab
2024-11-13 22:42 ` dpdklab
2024-11-14  0:30 ` |PENDING| " dpdklab
2024-11-14  0:46 ` |SUCCESS| " dpdklab
2024-11-14  1:09 ` dpdklab
2024-11-14  1:25 ` |PENDING| " dpdklab
2024-11-14  2:08 ` |SUCCESS| " dpdklab
2024-11-14  2:15 ` |WARNING| " dpdklab
2024-11-14  3:22 ` |SUCCESS| " dpdklab
2024-11-14  3:23 ` |WARNING| " dpdklab
2024-11-14  3:26 ` |SUCCESS| " dpdklab
2024-11-14  4:12 ` dpdklab
2024-11-14  6:14 ` dpdklab
2024-11-16 16:39 ` |WARNING| " dpdklab
2024-11-16 20:34 ` dpdklab [this message]
2024-11-16 21:21 ` dpdklab
2024-11-16 21:37 ` dpdklab
2024-11-16 21:44 ` 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=673901bd.250a0220.2a7ff2.747fSMTPIN_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).