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| pw142671-142673 [PATCH] [v3,3/3] test-pmd: add more packet
Date: Thu, 25 Jul 2024 11:18:17 -0700 (PDT)	[thread overview]
Message-ID: <66a296e9.050a0220.1dae5f.4b11SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240723203629.246735-4-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, July 23 2024 20:33:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9cad88310860ad99f9133af39f9cf98e524de9ac

142671-142673 --> testing pass

Upstream job id: ACVP-FIPS-testing#6393

Test environment and result as below:

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


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

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

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

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

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2024-07-25 18:18 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240723203629.246735-4-stephen@networkplumber.org>
2024-07-23 20:17 ` |SUCCESS| pw142671-142673 [PATCH v3 3/3] test-pmd: add more packet verbose decode options qemudev
2024-07-23 20:22 ` qemudev
2024-07-23 20:37 ` |WARNING| pw142673 " checkpatch
2024-07-23 21:23 ` |FAILURE| " 0-day Robot
2024-07-24  9:01 ` |PENDING| pw142671-142673 [PATCH] [v3,3/3] test-pmd: add more packet dpdklab
2024-07-24  9:06 ` dpdklab
2024-07-24  9:13 ` |SUCCESS| " dpdklab
2024-07-24  9:19 ` dpdklab
2024-07-24  9:37 ` dpdklab
2024-07-24  9:38 ` dpdklab
2024-07-24  9:45 ` |PENDING| " dpdklab
2024-07-24  9:46 ` |SUCCESS| " dpdklab
2024-07-24  9:58 ` dpdklab
2024-07-24  9:58 ` |PENDING| " dpdklab
2024-07-24 10:00 ` |SUCCESS| " dpdklab
2024-07-24 10:04 ` dpdklab
2024-07-24 10:08 ` dpdklab
2024-07-24 10:10 ` |PENDING| " dpdklab
2024-07-24 10:12 ` dpdklab
2024-07-24 10:12 ` dpdklab
2024-07-24 10:13 ` dpdklab
2024-07-24 10:13 ` dpdklab
2024-07-24 10:17 ` dpdklab
2024-07-24 10:19 ` dpdklab
2024-07-24 10:19 ` dpdklab
2024-07-24 10:19 ` dpdklab
2024-07-24 10:22 ` dpdklab
2024-07-24 10:23 ` dpdklab
2024-07-24 10:24 ` |SUCCESS| " dpdklab
2024-07-24 10:25 ` dpdklab
2024-07-24 10:27 ` dpdklab
2024-07-24 10:28 ` dpdklab
2024-07-24 10:35 ` dpdklab
2024-07-24 10:41 ` dpdklab
2024-07-24 11:03 ` dpdklab
2024-07-24 12:20 ` |FAILURE| " dpdklab
2024-07-24 12:21 ` |PENDING| " dpdklab
2024-07-24 12:21 ` |FAILURE| " dpdklab
2024-07-24 12:24 ` dpdklab
2024-07-24 12:24 ` dpdklab
2024-07-24 12:26 ` dpdklab
2024-07-24 12:27 ` dpdklab
2024-07-24 12:27 ` dpdklab
2024-07-24 12:28 ` dpdklab
2024-07-24 12:59 ` |PENDING| " dpdklab
2024-07-24 13:59 ` dpdklab
2024-07-24 14:03 ` |FAILURE| " dpdklab
2024-07-24 14:04 ` |PENDING| " dpdklab
2024-07-24 14:04 ` dpdklab
2024-07-24 14:05 ` |FAILURE| " dpdklab
2024-07-24 14:05 ` |PENDING| " dpdklab
2024-07-24 14:05 ` |FAILURE| " dpdklab
2024-07-24 14:05 ` dpdklab
2024-07-24 14:06 ` dpdklab
2024-07-24 14:07 ` |PENDING| " dpdklab
2024-07-24 14:08 ` |FAILURE| " dpdklab
2024-07-24 14:08 ` |PENDING| " dpdklab
2024-07-24 14:09 ` dpdklab
2024-07-24 14:10 ` dpdklab
2024-07-24 14:11 ` dpdklab
2024-07-24 14:11 ` dpdklab
2024-07-24 14:11 ` dpdklab
2024-07-24 14:12 ` dpdklab
2024-07-24 14:13 ` dpdklab
2024-07-24 14:14 ` |FAILURE| " dpdklab
2024-07-24 14:15 ` |PENDING| " dpdklab
2024-07-24 14:15 ` |FAILURE| " dpdklab
2024-07-24 14:18 ` dpdklab
2024-07-24 14:19 ` dpdklab
2024-07-24 14:22 ` dpdklab
2024-07-24 14:27 ` dpdklab
2024-07-24 14:28 ` |PENDING| " dpdklab
2024-07-24 14:29 ` |FAILURE| " dpdklab
2024-07-24 14:30 ` |PENDING| " dpdklab
2024-07-24 14:30 ` |FAILURE| " dpdklab
2024-07-24 14:35 ` dpdklab
2024-07-24 14:36 ` dpdklab
2024-07-24 14:36 ` dpdklab
2024-07-24 14:37 ` dpdklab
2024-07-24 14:37 ` dpdklab
2024-07-24 14:37 ` dpdklab
2024-07-24 14:38 ` dpdklab
2024-07-24 14:39 ` |PENDING| " dpdklab
2024-07-24 14:40 ` |FAILURE| " dpdklab
2024-07-24 14:40 ` dpdklab
2024-07-24 14:40 ` dpdklab
2024-07-24 14:41 ` dpdklab
2024-07-24 14:43 ` dpdklab
2024-07-24 14:46 ` |PENDING| " dpdklab
2024-07-24 14:46 ` dpdklab
2024-07-24 14:47 ` |FAILURE| " dpdklab
2024-07-24 14:51 ` dpdklab
2024-07-24 14:53 ` |PENDING| " dpdklab
2024-07-24 14:54 ` |FAILURE| " dpdklab
2024-07-24 14:55 ` |PENDING| " dpdklab
2024-07-24 14:56 ` |FAILURE| " dpdklab
2024-07-24 14:56 ` dpdklab
2024-07-24 14:56 ` dpdklab
2024-07-24 14:56 ` |PENDING| " dpdklab
2024-07-24 15:01 ` dpdklab
2024-07-24 15:03 ` dpdklab
2024-07-24 15:06 ` dpdklab
2024-07-24 15:11 ` |FAILURE| " dpdklab
2024-07-24 15:15 ` |PENDING| " dpdklab
2024-07-24 15:21 ` dpdklab
2024-07-24 15:21 ` dpdklab
2024-07-24 15:22 ` dpdklab
2024-07-24 15:25 ` dpdklab
2024-07-24 15:27 ` dpdklab
2024-07-24 15:29 ` dpdklab
2024-07-24 15:29 ` |SUCCESS| " dpdklab
2024-07-24 15:30 ` dpdklab
2024-07-24 15:34 ` |PENDING| " dpdklab
2024-07-24 15:44 ` |SUCCESS| " dpdklab
2024-07-25 18:18 ` dpdklab [this message]

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=66a296e9.050a0220.1dae5f.4b11SMTPIN_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).