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| pw147185-147190 [PATCH] [v2,6/6] drivers: use bitops API i
Date: Fri, 01 Nov 2024 18:46:14 -0700 (PDT)	[thread overview]
Message-ID: <67258466.050a0220.39748f.14c1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241025070424.3916007-7-david.marchand@redhat.com>

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, October 25 2024 07:04:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:90cb8ff8196f9b9c1c2bcee1c94ea583789bb63f

147185-147190 --> testing pass

Upstream job id: ACVP-FIPS-testing#7615

Test environment and result as below:

+--------------+----------------------+
| Environment  | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS                 |
+--------------+----------------------+


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

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  1:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241025070424.3916007-7-david.marchand@redhat.com>
2024-10-25  6:45 ` |SUCCESS| pw147185-147190 [PATCH v2 6/6] drivers: use bitops API instead of compiler builtins qemudev
2024-10-25  6:49 ` qemudev
2024-10-25  7:05 ` |SUCCESS| pw147190 " checkpatch
2024-10-25  8:07 ` 0-day Robot
2024-10-25 15:28 ` |SUCCESS| pw147185-147190 [PATCH] [v2,6/6] drivers: use bitops API i dpdklab
2024-10-25 15:50 ` dpdklab
2024-10-25 15:59 ` dpdklab
2024-10-26  4:20 ` dpdklab
2024-10-26  5:22 ` dpdklab
2024-10-26 17:12 ` dpdklab
2024-10-27  9:44 ` |PENDING| " dpdklab
2024-10-27 17:12 ` |SUCCESS| " dpdklab
2024-10-27 17:25 ` dpdklab
2024-10-28 10:04 ` |PENDING| " dpdklab
2024-10-28 11:58 ` |WARNING| " dpdklab
2024-10-28 15:51 ` dpdklab
2024-10-29  6:14 ` |PENDING| " dpdklab
2024-10-29  8:35 ` |SUCCESS| " dpdklab
2024-10-29  8:42 ` dpdklab
2024-11-01 19:43 ` dpdklab
2024-11-02  1:46 ` 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=67258466.050a0220.39748f.14c1SMTPIN_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).