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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw125145 [PATCH] [v2] vhost: fix madvise IOTLB entries pages overlap check
Date: Wed, 15 Mar 2023 12:54:02 +0000 (UTC)	[thread overview]
Message-ID: <20230315125402.D54856011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125145

_Functional Testing PASS_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Wednesday, March 15 2023 11:40:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:baf13c3135d0c5998fff7edc23fb89412dc89246

125145 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-03-15 12:54 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15 12:54 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-19  5:04 dpdklab
2023-03-19  5:03 dpdklab
2023-03-19  5:02 dpdklab
2023-03-19  4:58 dpdklab
2023-03-19  4:57 dpdklab
2023-03-19  4:48 dpdklab
2023-03-19  4:46 dpdklab
2023-03-19  4:44 dpdklab
2023-03-19  4:38 dpdklab
2023-03-19  4:33 dpdklab
2023-03-19  4:32 dpdklab
2023-03-19  4:28 dpdklab
2023-03-19  4:20 dpdklab
2023-03-19  4:16 dpdklab
2023-03-19  4:16 dpdklab
2023-03-19  4:12 dpdklab
2023-03-19  4:11 dpdklab
2023-03-19  4:04 dpdklab
2023-03-19  4:01 dpdklab
2023-03-19  3:57 dpdklab
2023-03-19  3:53 dpdklab
2023-03-19  3:51 dpdklab
2023-03-19  3:47 dpdklab
2023-03-19  3:46 dpdklab
2023-03-19  3:43 dpdklab
2023-03-19  3:38 dpdklab
2023-03-19  3:36 dpdklab
2023-03-19  2:57 dpdklab
2023-03-17 23:11 dpdklab
2023-03-17 21:50 dpdklab
2023-03-15 17:08 dpdklab
2023-03-15 16:24 dpdklab
2023-03-15 15:47 dpdklab
2023-03-15 15:08 dpdklab
2023-03-15 14:39 dpdklab
2023-03-15 14:36 dpdklab
2023-03-15 14:34 dpdklab
2023-03-15 14:22 dpdklab
2023-03-15 14:05 dpdklab
2023-03-15 13:53 dpdklab
2023-03-15 13:51 dpdklab
2023-03-15 13:47 dpdklab
2023-03-15 13:42 dpdklab
2023-03-15 13:42 dpdklab
2023-03-15 13:41 dpdklab
2023-03-15 13:39 dpdklab
2023-03-15 13:38 dpdklab
2023-03-15 13:38 dpdklab
2023-03-15 13:32 dpdklab
2023-03-15 13:28 dpdklab
2023-03-15 13:25 dpdklab
2023-03-15 13:20 dpdklab
2023-03-15 13:19 dpdklab
2023-03-15 13:15 dpdklab
2023-03-15 13:11 dpdklab
2023-03-15 13:06 dpdklab
2023-03-15 13:04 dpdklab
2023-03-15 13:04 dpdklab
2023-03-15 12:59 dpdklab
2023-03-15 12:59 dpdklab
2023-03-15 12:54 dpdklab
     [not found] <20230315114010.444005-1-maxime.coquelin@redhat.com>
2023-03-15 11:32 ` |SUCCESS| pw125145 [PATCH v2] " qemudev
2023-03-15 11:36 ` qemudev
2023-03-15 13:39 ` 0-day Robot

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=20230315125402.D54856011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).