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| pw147858 [PATCH] crypto/qat: fix ecdsa session handling
Date: Thu, 31 Oct 2024 14:01:26 -0700 (PDT)	[thread overview]
Message-ID: <6723f026.050a0220.2f9ac5.4fa8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241031191952.20863-1-arkadiuszx.kusztal@intel.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147858

_Testing PASS_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Thursday, October 31 2024 19:19:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f

147858 --> testing pass

Upstream job id: Generic-VM-DPDK-Compile-Meson#31004

Test environment and result as below:

+--------------+--------------------+
| Environment  | dpdk_meson_compile |
+==============+====================+
| FreeBSD 13.4 | PASS               |
+--------------+--------------------+


FreeBSD 13.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-31 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241031191952.20863-1-arkadiuszx.kusztal@intel.com>
2024-10-31 18:55 ` qemudev
2024-10-31 19:00 ` qemudev
2024-10-31 19:20 ` |WARNING| " checkpatch
2024-10-31 20:25 ` |SUCCESS| " 0-day Robot
2024-10-31 20:47 ` |PENDING| " dpdklab
2024-10-31 21:01 ` dpdklab [this message]
2024-10-31 21:17 ` |SUCCESS| " dpdklab
2024-10-31 21:17 ` dpdklab
2024-10-31 23:11 ` |PENDING| " 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=6723f026.050a0220.2f9ac5.4fa8SMTPIN_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).