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| pw135978 [PATCH] telemetry: correct json empty dictionarie
Date: Fri, 19 Jan 2024 12:36:16 -0800 (PST)	[thread overview]
Message-ID: <65aadd40.050a0220.76b39.00b7SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Jonathan Erb <jonathan.erb@threater.com>
Date: Thursday, January 18 2024 17:26:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:775ff373216c56acfeffe862c20af2f216c049ea

135978 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+


FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-19 20:36 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 20:36 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 16:41 dpdklab
2024-01-22 16:34 dpdklab
2024-01-20 10:57 dpdklab
2024-01-20  0:20 dpdklab
2024-01-20  0:14 dpdklab
2024-01-19 23:44 dpdklab
2024-01-19 23:20 dpdklab
2024-01-19 22:31 dpdklab
2024-01-19 22:27 dpdklab
2024-01-19 22:27 dpdklab
2024-01-19 22:17 dpdklab
2024-01-19 22:16 dpdklab
2024-01-19 22:14 dpdklab
2024-01-19 22:12 dpdklab
2024-01-19 22:11 dpdklab
2024-01-19 22:11 dpdklab
2024-01-19 22:10 dpdklab
2024-01-19 22:10 dpdklab
2024-01-19 22:09 dpdklab
2024-01-19 22:07 dpdklab
2024-01-19 22:07 dpdklab
2024-01-19 22:07 dpdklab
2024-01-19 22:07 dpdklab
2024-01-19 22:05 dpdklab
2024-01-19 22:02 dpdklab
2024-01-19 22:02 dpdklab
2024-01-19 22:01 dpdklab
2024-01-19 21:54 dpdklab
2024-01-19 21:53 dpdklab
2024-01-19 21:46 dpdklab
2024-01-19 21:44 dpdklab
2024-01-19 21:44 dpdklab
2024-01-19 21:42 dpdklab
2024-01-19 21:42 dpdklab
2024-01-19 21:41 dpdklab
2024-01-19 21:40 dpdklab
2024-01-19 21:40 dpdklab
2024-01-19 21:34 dpdklab
2024-01-19 21:13 dpdklab
2024-01-19 21:06 dpdklab
2024-01-19 20:51 dpdklab
2024-01-19 20:45 dpdklab
2024-01-19 20:44 dpdklab
2024-01-19 20:44 dpdklab
2024-01-19 20:40 dpdklab
2024-01-19 20:39 dpdklab
2024-01-19 20:37 dpdklab
2024-01-19 20:36 dpdklab
2024-01-19 20:35 dpdklab
2024-01-19 20:30 dpdklab
2024-01-19 20:30 dpdklab
2024-01-19 20:30 dpdklab
2024-01-19 20:28 dpdklab
2024-01-19 20:27 dpdklab
2024-01-19 20:27 dpdklab
2024-01-19 20:26 dpdklab
2024-01-19 20:15 dpdklab
2024-01-19 20:14 dpdklab
2024-01-19 20:08 dpdklab
2024-01-19 19:27 dpdklab
2024-01-19 19:27 dpdklab
2024-01-19 19:25 dpdklab
2024-01-19 19:25 dpdklab
2024-01-19 19:24 dpdklab
2024-01-19 19:24 dpdklab
2024-01-19 19:24 dpdklab
2024-01-19 19:20 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=65aadd40.050a0220.76b39.00b7SMTPIN_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).