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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125857 [PATCH] doc: fix event timer adapter guide
Date: Fri,  7 Apr 2023 17:48:21 +0000 (UTC)	[thread overview]
Message-ID: <20230407174821.1CE826012C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/125857

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Friday, April 07 2023 08:14:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:65487b12db83c9ef37526a983c43191cd44dae99

125857 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+


Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-07 17:48 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 17:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-07 19:35 dpdklab
2023-04-07 19:12 dpdklab
2023-04-07 19:10 dpdklab
2023-04-07 18:20 dpdklab
2023-04-07 18:12 dpdklab
2023-04-07 18:11 dpdklab
2023-04-07 18:10 dpdklab
2023-04-07 18:02 dpdklab
2023-04-07 17:59 dpdklab
2023-04-07 17:49 dpdklab
2023-04-07 17:44 dpdklab
2023-04-07 17:39 dpdklab
2023-04-07 17:38 dpdklab
2023-04-07 17:32 dpdklab
2023-04-07 17:16 dpdklab
2023-04-07 17:12 dpdklab
2023-04-07 17:11 dpdklab
2023-04-07 17:11 dpdklab
2023-04-07 17:09 dpdklab
2023-04-07 17:06 dpdklab
2023-04-07 17:04 dpdklab
2023-04-07 17:03 dpdklab
2023-04-07 17:01 dpdklab
2023-04-07 16:59 dpdklab
2023-04-07 16:58 dpdklab
2023-04-07 16:58 dpdklab
2023-04-07 16:54 dpdklab
2023-04-07 16:53 dpdklab
2023-04-07 16:51 dpdklab
2023-04-07 16:45 dpdklab
2023-04-07 16:42 dpdklab
2023-04-07 16:41 dpdklab
2023-04-07 16:41 dpdklab
2023-04-07 16:37 dpdklab
2023-04-07 16:35 dpdklab
2023-04-07 16:35 dpdklab
2023-04-07 16:30 dpdklab
2023-04-07 16:28 dpdklab
2023-04-07 16:25 dpdklab
2023-04-07 16:07 dpdklab
2023-04-07 15:59 dpdklab
2023-04-07 15:54 dpdklab
2023-04-07 15:51 dpdklab
2023-04-07 15:49 dpdklab
2023-04-07 15:47 dpdklab
2023-04-07 15:45 dpdklab
2023-04-07 15:45 dpdklab
2023-04-07 15:44 dpdklab
2023-04-07 15:43 dpdklab
2023-04-07 15:42 dpdklab
2023-04-07 15:38 dpdklab
2023-04-07 15:36 dpdklab
     [not found] <20230407081410.1714-1-pbhagavatula@marvell.com>
2023-04-07  8:02 ` qemudev
2023-04-07  8:06 ` qemudev
2023-04-07  8:15 ` checkpatch
2023-04-07  9:18 ` 0-day Robot

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=20230407174821.1CE826012C@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).