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| pw143421 [PATCH] bus/pci: don't open uio device in seconda
Date: Wed, 28 Aug 2024 05:39:06 -0700 (PDT)	[thread overview]
Message-ID: <66cf1a6a.050a0220.2e9526.4536SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240828104002.226704-1-konrad.sztyber@intel.com>

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

_Functional Testing PASS_

Submitter: Konrad Sztyber <konrad.sztyber@intel.com>
Date: Wednesday, August 28 2024 10:40:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143421 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#177438

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-28 12:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240828104002.226704-1-konrad.sztyber@intel.com>
2024-08-28 10:14 ` |SUCCESS| pw143421 [PATCH] bus/pci: don't open uio device in secondary process qemudev
2024-08-28 10:19 ` qemudev
2024-08-28 10:41 ` |WARNING| " checkpatch
2024-08-28 11:43 ` |SUCCESS| " 0-day Robot
2024-08-28 12:16 ` |SUCCESS| pw143421 [PATCH] bus/pci: don't open uio device in seconda dpdklab
2024-08-28 12:18 ` dpdklab
2024-08-28 12:19 ` dpdklab
2024-08-28 12:20 ` dpdklab
2024-08-28 12:21 ` dpdklab
2024-08-28 12:21 ` dpdklab
2024-08-28 12:34 ` dpdklab
2024-08-28 12:37 ` dpdklab
2024-08-28 12:39 ` dpdklab [this message]
2024-08-28 12:44 ` dpdklab
2024-08-28 12:47 ` |FAILURE| " dpdklab
2024-08-28 12:48 ` dpdklab
2024-08-28 12:49 ` dpdklab
2024-08-28 12:49 ` dpdklab
2024-08-28 12:51 ` |SUCCESS| " dpdklab
2024-08-28 12:54 ` |FAILURE| " dpdklab
2024-08-28 13:17 ` |SUCCESS| " dpdklab
2024-08-28 13:21 ` dpdklab
2024-08-28 13:27 ` dpdklab
2024-08-28 13:56 ` dpdklab
2024-08-28 14:12 ` dpdklab
2024-08-28 15:40 ` dpdklab
2024-08-28 19:27 ` |FAILURE| " dpdklab
2024-08-28 19:34 ` |SUCCESS| " dpdklab
2024-09-19 17:40 ` dpdklab
2024-09-19 18:20 ` 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=66cf1a6a.050a0220.2e9526.4536SMTPIN_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).