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| pw136239-136240 [PATCH] [v2,2/2] vhost: add new mbuf alloc
Date: Wed, 31 Jan 2024 12:57:53 -0800 (PST)	[thread overview]
Message-ID: <65bab451.020a0220.dd90d.20f1SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Wednesday, January 31 2024 19:53:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8117c2e31423d967087e7771d6ab6c875dfd19d9

136239-136240 --> testing pass

Test environment and result as below:

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


Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-31 20:57 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 20:57 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-31 21:55 dpdklab
2024-01-31 21:36 dpdklab
2024-01-31 21:13 dpdklab
2024-01-31 21:07 dpdklab
2024-01-31 21:05 dpdklab
2024-01-31 21:01 dpdklab
2024-01-31 21:01 dpdklab
2024-01-31 21:01 dpdklab
2024-01-31 21:00 dpdklab
2024-01-31 21:00 dpdklab
2024-01-31 20:58 dpdklab
2024-01-31 20:58 dpdklab
2024-01-31 20:57 dpdklab
2024-01-31 20:56 dpdklab
2024-01-31 20:56 dpdklab
2024-01-31 20:55 dpdklab
2024-01-31 20:53 dpdklab
2024-01-31 20:52 dpdklab
2024-01-31 20:51 dpdklab
2024-01-31 20:50 dpdklab
2024-01-31 20:49 dpdklab
2024-01-31 20:49 dpdklab
2024-01-31 20:48 dpdklab
2024-01-31 20:48 dpdklab
2024-01-31 20:46 dpdklab
2024-01-31 20:46 dpdklab
2024-01-31 20:46 dpdklab
2024-01-31 20:46 dpdklab
2024-01-31 20:46 dpdklab
2024-01-31 20:45 dpdklab
2024-01-31 20:45 dpdklab
2024-01-31 20:45 dpdklab
2024-01-31 20:45 dpdklab
2024-01-31 20:43 dpdklab
2024-01-31 20:43 dpdklab
2024-01-31 20:42 dpdklab
2024-01-31 20:42 dpdklab
2024-01-31 20:42 dpdklab
2024-01-31 20:42 dpdklab
2024-01-31 20:42 dpdklab
2024-01-31 20:41 dpdklab
2024-01-31 20:41 dpdklab
2024-01-31 20:40 dpdklab
2024-01-31 20:40 dpdklab
2024-01-31 20:40 dpdklab
2024-01-31 20:40 dpdklab
2024-01-31 20:40 dpdklab
2024-01-31 20:40 dpdklab
2024-01-31 20:39 dpdklab
2024-01-31 20:39 dpdklab
2024-01-31 20:39 dpdklab
2024-01-31 20:39 dpdklab
2024-01-31 20:38 dpdklab
2024-01-31 20:38 dpdklab
2024-01-31 20:38 dpdklab
2024-01-31 20:38 dpdklab
2024-01-31 20:37 dpdklab
2024-01-31 20:37 dpdklab
2024-01-31 20:37 dpdklab
2024-01-31 20:37 dpdklab
2024-01-31 20:36 dpdklab
2024-01-31 20:36 dpdklab
2024-01-31 20:36 dpdklab
2024-01-31 20:35 dpdklab
2024-01-31 20:34 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=65bab451.020a0220.dd90d.20f1SMTPIN_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).