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| pw147521-147542 [PATCH] [v8,22/22] event/cnxk: add CN20K t
Date: Tue, 05 Nov 2024 09:39:38 -0800 (PST)	[thread overview]
Message-ID: <672a585a.170a0220.2c3c58.78deSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241028155923.30287-22-pbhagavatula@marvell.com>

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

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Monday, October 28 2024 15:59:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a682d65f8dbe1e8be9cc2425095827e18c700e3

147521-147542 --> testing pass

Upstream job id: ACVP-FIPS-testing#7757

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: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2024-11-05 17:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241028155923.30287-22-pbhagavatula@marvell.com>
2024-10-28 15:50 ` |SUCCESS| pw147521-147542 [PATCH v8 22/22] event/cnxk: add CN20K timer adapter qemudev
2024-10-28 15:55 ` qemudev
2024-10-28 16:05 ` |WARNING| pw147542 " checkpatch
2024-10-28 17:06 ` |SUCCESS| " 0-day Robot
2024-10-31 18:26 ` |SUCCESS| pw147521-147542 [PATCH] [v8,22/22] event/cnxk: add CN20K t dpdklab
2024-10-31 19:03 ` |PENDING| " dpdklab
2024-10-31 19:25 ` dpdklab
2024-10-31 19:38 ` |SUCCESS| " dpdklab
2024-10-31 20:00 ` |PENDING| " dpdklab
2024-10-31 20:51 ` |SUCCESS| " dpdklab
2024-10-31 20:59 ` dpdklab
2024-10-31 21:14 ` dpdklab
2024-10-31 22:01 ` dpdklab
2024-10-31 22:29 ` dpdklab
2024-10-31 22:30 ` dpdklab
2024-11-01  3:27 ` |PENDING| " dpdklab
2024-11-01  3:59 ` |SUCCESS| " dpdklab
2024-11-01  5:54 ` dpdklab
2024-11-01  7:46 ` dpdklab
2024-11-01 11:58 ` dpdklab
2024-11-01 15:16 ` dpdklab
2024-11-01 20:05 ` dpdklab
2024-11-01 20:40 ` dpdklab
2024-11-02 10:20 ` dpdklab
2024-11-02 19:28 ` dpdklab
2024-11-02 23:42 ` dpdklab
2024-11-02 23:44 ` dpdklab
2024-11-05 17:39 ` 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=672a585a.170a0220.2c3c58.78deSMTPIN_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).