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| pw148548 [PATCH] [v2] eal/linux: fix fbarray name with mul
Date: Fri, 15 Nov 2024 12:14:25 -0800 (PST)	[thread overview]
Message-ID: <6737aba1.a70a0220.34ad5a.6ba2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <tencent_0B9C25BDE8192439C88141D4EFDC0BEB8D07@qq.com>

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

_Functional Testing PASS_

Submitter: Congjie Zhou <zcjie0802@qq.com>
Date: Friday, November 15 2024 07:50:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:78383e9816a8efe2ba16ec2ce65d51b94e6114e7

148548 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#196764

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/31945/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-11-15 20:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tencent_0B9C25BDE8192439C88141D4EFDC0BEB8D07@qq.com>
2024-11-15  7:26 ` |FAILURE| pw148548 [PATCH v2] eal/linux: fix fbarray name with multiple secondary processes qemudev
2024-11-15  7:52 ` |SUCCESS| " checkpatch
2024-11-15  8:45 ` |FAILURE| " 0-day Robot
2024-11-15 19:37 ` |SUCCESS| pw148548 [PATCH] [v2] eal/linux: fix fbarray name with mul dpdklab
2024-11-15 19:41 ` dpdklab
2024-11-15 19:53 ` |FAILURE| " dpdklab
2024-11-15 19:54 ` |SUCCESS| " dpdklab
2024-11-15 19:56 ` |PENDING| " dpdklab
2024-11-15 20:09 ` |FAILURE| " dpdklab
2024-11-15 20:09 ` dpdklab
2024-11-15 20:10 ` dpdklab
2024-11-15 20:11 ` dpdklab
2024-11-15 20:13 ` dpdklab
2024-11-15 20:14 ` dpdklab [this message]
2024-11-15 20:27 ` |SUCCESS| " dpdklab
2024-11-15 20:32 ` |FAILURE| " dpdklab
2024-11-15 20:33 ` dpdklab
2024-11-15 20:33 ` dpdklab
2024-11-15 20:45 ` |SUCCESS| " dpdklab
2024-11-15 21:09 ` dpdklab
2024-11-15 21:14 ` |WARNING| " dpdklab
2024-11-15 21:14 ` 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=6737aba1.a70a0220.34ad5a.6ba2SMTPIN_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).