automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: |SUCCESS| pw136632 [PATCH] maintainers: add myself to usertools
Date: Tue, 13 Feb 2024 03:36:53 -0800 (PST)	[thread overview]
Message-ID: <65cb5455.050a0220.57323.051eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136632

_Testing PASS_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Tuesday, February 13 2024 09:58:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2ea7994ae39ff979b15899ec9eb9c68c944d4b11

136632 --> testing pass

Test environment and result as below:

+--------------+----------------------+----------------------+
| Environment  | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | PASS                 | SKIPPED              |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED              | PASS                 |
+--------------+----------------------+----------------------+


Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 22.04
	Kernel: 5.15.0-91-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-13 11:36 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 11:36 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-13 12:04 dpdklab
2024-02-13 11:37 dpdklab
2024-02-13 11:36 dpdklab
2024-02-13 11:23 dpdklab
2024-02-13 11:22 dpdklab
2024-02-13 11:22 dpdklab
2024-02-13 11:19 dpdklab
2024-02-13 11:06 dpdklab
2024-02-13 11:03 dpdklab
2024-02-13 10:58 dpdklab
2024-02-13 10:58 dpdklab
2024-02-13 10:58 dpdklab
2024-02-13 10:57 dpdklab
2024-02-13 10:57 dpdklab
2024-02-13 10:57 dpdklab
2024-02-13 10:57 dpdklab
2024-02-13 10:56 dpdklab
2024-02-13 10:56 dpdklab
2024-02-13 10:56 dpdklab
2024-02-13 10:56 dpdklab
2024-02-13 10:54 dpdklab
2024-02-13 10:54 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:53 dpdklab
2024-02-13 10:52 dpdklab
2024-02-13 10:52 dpdklab
2024-02-13 10:52 dpdklab
2024-02-13 10:51 dpdklab
2024-02-13 10:51 dpdklab
2024-02-13 10:51 dpdklab
2024-02-13 10:51 dpdklab
2024-02-13 10:50 dpdklab
2024-02-13 10:50 dpdklab
2024-02-13 10:49 dpdklab
2024-02-13 10:49 dpdklab
2024-02-13 10:49 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:48 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:47 dpdklab
2024-02-13 10:46 dpdklab
2024-02-13 10:46 dpdklab
2024-02-13 10:45 dpdklab
2024-02-13 10:45 dpdklab
2024-02-13 10:44 dpdklab
2024-02-13 10:44 dpdklab
2024-02-13 10:44 dpdklab
2024-02-13 10:43 dpdklab
2024-02-13 10:43 dpdklab
2024-02-13 10:43 dpdklab
2024-02-13 10:43 dpdklab
2024-02-13 10:42 dpdklab
2024-02-13 10:42 dpdklab
2024-02-13 10:41 dpdklab
2024-02-13 10:33 dpdklab
2024-02-13 10:33 dpdklab
2024-02-13 10:32 dpdklab
2024-02-13 10:32 dpdklab
2024-02-13 10:32 dpdklab
     [not found] <20240213095851.60315-2-rjarry@redhat.com>
2024-02-13  9:37 ` qemudev
2024-02-13  9:41 ` qemudev
2024-02-13  9:59 ` checkpatch
2024-02-13 11:04 ` 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=65cb5455.050a0220.57323.051eSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@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).