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| pw145189 [PATCH] maintainers: update for dts
Date: Fri, 04 Oct 2024 20:11:26 -0700 (PDT)	[thread overview]
Message-ID: <6700ae5e.050a0220.225f95.2b68SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241004191811.261865-1-probb@iol.unh.edu>

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

_Functional Testing PASS_

Submitter: Patrick Robb <probb@iol.unh.edu>
Date: Friday, October 04 2024 19:18:06 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41b09d64e35b877e8f29c4e5a8cf944e303695dd

145189 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#185474

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 XL710-QDA2 40000 Mbps

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


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 |
+=============================+========+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


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

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-05  3:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241004191811.261865-1-probb@iol.unh.edu>
2024-10-04 18:52 ` qemudev
2024-10-04 18:57 ` qemudev
2024-10-04 19:20 ` checkpatch
2024-10-04 20:23 ` 0-day Robot
2024-10-05  1:06 ` |PENDING| " dpdklab
2024-10-05  1:13 ` |SUCCESS| " dpdklab
2024-10-05  1:17 ` dpdklab
2024-10-05  1:29 ` dpdklab
2024-10-05  1:31 ` dpdklab
2024-10-05  1:31 ` dpdklab
2024-10-05  1:52 ` dpdklab
2024-10-05  1:55 ` |PENDING| " dpdklab
2024-10-05  1:55 ` dpdklab
2024-10-05  2:32 ` |SUCCESS| " dpdklab
2024-10-05  2:58 ` dpdklab
2024-10-05  2:59 ` dpdklab
2024-10-05  3:07 ` dpdklab
2024-10-05  3:11 ` dpdklab [this message]
2024-10-05  3:19 ` |PENDING| " dpdklab
2024-10-05  3:37 ` |SUCCESS| " dpdklab
2024-10-05  4:44 ` dpdklab
2024-10-05  5:04 ` dpdklab
2024-10-05  5:04 ` 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=6700ae5e.050a0220.225f95.2b68SMTPIN_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).