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| pw122885-122886 [PATCH] [2/2] event/cnxk: update timer arm burst parameters
Date: Thu,  2 Feb 2023 17:30:21 +0000 (UTC)	[thread overview]
Message-ID: <20230202173021.F26E3600AE@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

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

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thursday, February 02 2023 08:10:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5003661613fa7663347b7ea75f2560b8a6458a30

122885-122886 --> 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/25162/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-02 17:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 17:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-04  1:47 dpdklab
2023-02-03 19:12 dpdklab
2023-02-03 14:26 dpdklab
2023-02-03  0:37 dpdklab
2023-02-03  0:37 dpdklab
2023-02-03  0:37 dpdklab
2023-02-03  0:36 dpdklab
2023-02-03  0:36 dpdklab
2023-02-03  0:36 dpdklab
2023-02-03  0:36 dpdklab
2023-02-03  0:24 dpdklab
2023-02-03  0:24 dpdklab
2023-02-02 17:30 dpdklab
2023-02-02  9:19 dpdklab
2023-02-02  9:10 dpdklab
2023-02-02  9:05 dpdklab
2023-02-02  9:04 dpdklab
2023-02-02  8:59 dpdklab
2023-02-02  8:51 dpdklab
2023-02-02  8:48 dpdklab
2023-02-02  8:46 dpdklab
     [not found] <20230202081025.4176-2-pbhagavatula@marvell.com>
2023-02-02  8:05 ` |SUCCESS| pw122885-122886 [PATCH 2/2] " qemudev
2023-02-02  8:09 ` qemudev
2023-02-02 11:56 ` qemudev
2023-02-03 10:51 ` qemudev
2023-02-03 10:56 ` qemudev

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=20230202173021.F26E3600AE@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).