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| pw146610 [PATCH] event/cnxk: fix getwork write data on rec
Date: Sat, 02 Nov 2024 09:59:56 -0700 (PDT)	[thread overview]
Message-ID: <67265a8c.050a0220.225c6f.b347SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241022122339.18255-1-pbhagavatula@marvell.com>

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

_Testing PASS_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tuesday, October 22 2024 12:23:39 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e609858b480ca0d646e5f05f2c7fd6bbf35a4140

146610 --> testing pass

Upstream job id: ACVP-FIPS-testing#7641

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

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-02 16:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241022122339.18255-1-pbhagavatula@marvell.com>
2024-10-22 12:01 ` |SUCCESS| pw146610 [PATCH] event/cnxk: fix getwork write data on reconfig qemudev
2024-10-22 12:05 ` qemudev
2024-10-22 12:25 ` checkpatch
2024-10-22 13:24 ` 0-day Robot
2024-10-23  4:10 ` |SUCCESS| pw146610 [PATCH] event/cnxk: fix getwork write data on rec dpdklab
2024-10-23  4:24 ` dpdklab
2024-10-23  4:56 ` dpdklab
2024-10-23  5:13 ` dpdklab
2024-10-23  5:24 ` dpdklab
2024-10-23  5:30 ` dpdklab
2024-10-23  5:41 ` dpdklab
2024-10-23  5:44 ` dpdklab
2024-10-23  6:02 ` dpdklab
2024-10-23  6:20 ` dpdklab
2024-10-23  7:02 ` dpdklab
2024-10-23  7:38 ` dpdklab
2024-10-23  7:57 ` dpdklab
2024-10-23  8:34 ` dpdklab
2024-10-24  5:41 ` dpdklab
2024-10-24  5:50 ` |PENDING| " dpdklab
2024-10-24  5:58 ` |SUCCESS| " dpdklab
2024-10-24  6:25 ` |WARNING| " dpdklab
2024-10-24  6:36 ` |SUCCESS| " dpdklab
2024-10-24  6:37 ` dpdklab
2024-10-24  8:05 ` dpdklab
2024-10-25  5:20 ` |PENDING| " dpdklab
2024-10-26  3:13 ` dpdklab
2024-10-26 13:44 ` |SUCCESS| " dpdklab
2024-10-27  9:25 ` dpdklab
2024-10-29 22:45 ` |WARNING| " dpdklab
2024-11-02  4:20 ` |SUCCESS| " dpdklab
2024-11-02 16:59 ` 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=67265a8c.050a0220.225c6f.b347SMTPIN_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).