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| pw143968 [PATCH] [v2] dts: correct typos in user config do
Date: Wed, 11 Sep 2024 12:46:56 -0700 (PDT)	[thread overview]
Message-ID: <66e1f3b0.810a0220.1ceb9.97c7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240911185229.13825-1-dmarx@iol.unh.edu>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143968

_Functional Testing PASS_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Wednesday, September 11 2024 18:52:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

143968 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#179979

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-11 19:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240911185229.13825-1-dmarx@iol.unh.edu>
2024-09-11 18:25 ` |SUCCESS| pw143968 [PATCH v2] dts: correct typos in user config docstrings qemudev
2024-09-11 18:29 ` qemudev
2024-09-11 18:52 ` checkpatch
2024-09-11 19:44 ` 0-day Robot
2024-09-11 19:46 ` dpdklab [this message]
2024-09-11 19:51 ` |SUCCESS| pw143968 [PATCH] [v2] dts: correct typos in user config do dpdklab
2024-09-11 20:00 ` dpdklab
2024-09-11 21:21 ` dpdklab
2024-09-11 21:42 ` |PENDING| " dpdklab
2024-09-11 21:46 ` |FAILURE| " dpdklab
2024-09-11 21:47 ` dpdklab
2024-09-11 21:47 ` dpdklab
2024-09-11 22:08 ` |PENDING| " dpdklab
2024-09-11 22:09 ` |WARNING| " dpdklab
2024-09-11 22:26 ` |PENDING| " dpdklab
2024-09-11 22:30 ` |SUCCESS| " dpdklab
2024-09-11 22:31 ` dpdklab
2024-09-11 22:31 ` dpdklab
2024-09-11 22:48 ` dpdklab
2024-09-11 22:53 ` dpdklab
2024-09-11 22:59 ` dpdklab
2024-09-11 23:03 ` dpdklab
2024-09-11 23:13 ` dpdklab
2024-09-11 23:13 ` dpdklab
2024-09-11 23:14 ` dpdklab
2024-09-11 23:20 ` dpdklab
2024-09-11 23:20 ` dpdklab
2024-09-11 23:21 ` dpdklab
2024-09-11 23:23 ` dpdklab
2024-09-12  0:35 ` dpdklab
2024-09-12  6:05 ` dpdklab
2024-09-15 15:33 ` dpdklab
2024-09-15 20:17 ` 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=66e1f3b0.810a0220.1ceb9.97c7SMTPIN_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).