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| pw142481 [PATCH] net/mlx5: fix end condition of reading xs
Date: Wed, 17 Jul 2024 14:55:10 -0700 (PDT)	[thread overview]
Message-ID: <66983dbe.b00a0220.f3b02.8045SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240717163337.324741-1-bingz@nvidia.com>

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

_Testing PASS_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Wednesday, July 17 2024 16:33:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142481 --> testing pass

Upstream job id: ACVP-FIPS-testing#6300

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

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-17 21:55 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240717163337.324741-1-bingz@nvidia.com>
2024-07-17 16:07 ` |SUCCESS| pw142481 [PATCH] net/mlx5: fix end condition of reading xstats qemudev
2024-07-17 16:11 ` qemudev
2024-07-17 16:35 ` checkpatch
2024-07-17 17:23 ` 0-day Robot
2024-07-17 18:30 ` |SUCCESS| pw142481 [PATCH] net/mlx5: fix end condition of reading xs dpdklab
2024-07-17 18:31 ` dpdklab
2024-07-17 18:38 ` dpdklab
2024-07-17 18:39 ` dpdklab
2024-07-17 18:43 ` dpdklab
2024-07-17 18:51 ` dpdklab
2024-07-17 18:52 ` dpdklab
2024-07-17 18:53 ` |PENDING| " dpdklab
2024-07-17 18:55 ` dpdklab
2024-07-17 18:55 ` dpdklab
2024-07-17 18:58 ` |SUCCESS| " dpdklab
2024-07-17 19:00 ` |PENDING| " dpdklab
2024-07-17 19:00 ` |SUCCESS| " dpdklab
2024-07-17 19:04 ` dpdklab
2024-07-17 19:08 ` |PENDING| " dpdklab
2024-07-17 19:08 ` dpdklab
2024-07-17 19:11 ` dpdklab
2024-07-17 19:15 ` |SUCCESS| " dpdklab
2024-07-17 19:15 ` |PENDING| " dpdklab
2024-07-17 19:17 ` dpdklab
2024-07-17 19:21 ` dpdklab
2024-07-17 19:22 ` |SUCCESS| " dpdklab
2024-07-17 19:22 ` |PENDING| " dpdklab
2024-07-17 19:23 ` dpdklab
2024-07-17 19:27 ` dpdklab
2024-07-17 19:27 ` |SUCCESS| " dpdklab
2024-07-17 19:28 ` |PENDING| " dpdklab
2024-07-17 19:28 ` dpdklab
2024-07-17 19:29 ` dpdklab
2024-07-17 19:32 ` |SUCCESS| " dpdklab
2024-07-17 19:32 ` |PENDING| " dpdklab
2024-07-17 19:33 ` dpdklab
2024-07-17 19:36 ` dpdklab
2024-07-17 19:36 ` |SUCCESS| " dpdklab
2024-07-17 19:37 ` |PENDING| " dpdklab
2024-07-17 19:42 ` dpdklab
2024-07-17 19:45 ` dpdklab
2024-07-17 19:45 ` dpdklab
2024-07-17 19:46 ` dpdklab
2024-07-17 19:46 ` dpdklab
2024-07-17 19:47 ` dpdklab
2024-07-17 19:48 ` dpdklab
2024-07-17 19:49 ` dpdklab
2024-07-17 19:49 ` dpdklab
2024-07-17 19:50 ` dpdklab
2024-07-17 19:51 ` dpdklab
2024-07-17 19:52 ` dpdklab
2024-07-17 19:54 ` dpdklab
2024-07-17 19:56 ` dpdklab
2024-07-17 19:57 ` dpdklab
2024-07-17 19:58 ` dpdklab
2024-07-17 19:58 ` dpdklab
2024-07-17 19:58 ` dpdklab
2024-07-17 19:59 ` dpdklab
2024-07-17 19:59 ` dpdklab
2024-07-17 19:59 ` |SUCCESS| " dpdklab
2024-07-17 20:00 ` |PENDING| " dpdklab
2024-07-17 20:00 ` dpdklab
2024-07-17 20:01 ` dpdklab
2024-07-17 20:02 ` dpdklab
2024-07-17 20:03 ` dpdklab
2024-07-17 20:04 ` dpdklab
2024-07-17 20:06 ` dpdklab
2024-07-17 20:07 ` dpdklab
2024-07-17 20:07 ` dpdklab
2024-07-17 20:08 ` dpdklab
2024-07-17 20:08 ` dpdklab
2024-07-17 20:09 ` dpdklab
2024-07-17 20:10 ` dpdklab
2024-07-17 20:16 ` |SUCCESS| " dpdklab
2024-07-17 20:25 ` |PENDING| " dpdklab
2024-07-17 20:27 ` dpdklab
2024-07-17 20:31 ` dpdklab
2024-07-17 20:33 ` dpdklab
2024-07-17 20:36 ` dpdklab
2024-07-17 20:41 ` dpdklab
2024-07-17 20:43 ` dpdklab
2024-07-17 20:45 ` dpdklab
2024-07-17 20:47 ` dpdklab
2024-07-17 20:50 ` dpdklab
2024-07-17 20:50 ` dpdklab
2024-07-17 20:50 ` dpdklab
2024-07-17 20:53 ` dpdklab
2024-07-17 20:55 ` dpdklab
2024-07-17 20:59 ` dpdklab
2024-07-17 20:59 ` dpdklab
2024-07-17 21:00 ` dpdklab
2024-07-17 21:02 ` dpdklab
2024-07-17 21:03 ` dpdklab
2024-07-17 21:03 ` dpdklab
2024-07-17 21:04 ` dpdklab
2024-07-17 21:04 ` dpdklab
2024-07-17 21:04 ` dpdklab
2024-07-17 21:04 ` dpdklab
2024-07-17 21:05 ` dpdklab
2024-07-17 21:07 ` dpdklab
2024-07-17 21:08 ` |SUCCESS| " dpdklab
2024-07-17 21:08 ` |PENDING| " dpdklab
2024-07-17 21:10 ` dpdklab
2024-07-17 21:11 ` dpdklab
2024-07-17 21:14 ` dpdklab
2024-07-17 21:14 ` dpdklab
2024-07-17 21:16 ` dpdklab
2024-07-17 21:17 ` dpdklab
2024-07-17 21:17 ` dpdklab
2024-07-17 21:20 ` dpdklab
2024-07-17 21:23 ` |SUCCESS| " dpdklab
2024-07-17 21:23 ` |PENDING| " dpdklab
2024-07-17 21:28 ` |SUCCESS| " dpdklab
2024-07-17 21:37 ` |PENDING| " dpdklab
2024-07-17 21:55 ` dpdklab [this message]
2024-07-17 22:03 ` |SUCCESS| " 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=66983dbe.b00a0220.f3b02.8045SMTPIN_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).