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| pw142650 [PATCH] rel_notes: announce 24.11 ipv6 api breaka
Date: Mon, 22 Jul 2024 16:06:09 -0700 (PDT)	[thread overview]
Message-ID: <669ee5e1.050a0220.7f616.9bebSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240722173936.24303-2-rjarry@redhat.com>

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

_Functional Testing PASS_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Monday, July 22 2024 17:39:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:79daa287a6733a753c87989621394567408f3345

142650 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#169780

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps

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


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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-22 23:06 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240722173936.24303-2-rjarry@redhat.com>
2024-07-22 17:12 ` |SUCCESS| pw142650 [PATCH dpdk] rel_notes: announce 24.11 ipv6 api breakage qemudev
2024-07-22 17:17 ` qemudev
2024-07-22 17:40 ` checkpatch
2024-07-22 18:44 ` 0-day Robot
2024-07-22 22:49 ` |SUCCESS| pw142650 [PATCH] rel_notes: announce 24.11 ipv6 api breaka dpdklab
2024-07-22 22:53 ` dpdklab
2024-07-22 22:57 ` dpdklab
2024-07-22 22:59 ` dpdklab
2024-07-22 23:06 ` dpdklab [this message]
2024-07-22 23:10 ` dpdklab
2024-07-22 23:12 ` dpdklab
2024-07-22 23:20 ` dpdklab
2024-07-22 23:36 ` dpdklab
2024-07-22 23:46 ` |PENDING| " dpdklab
2024-07-23  0:01 ` dpdklab
2024-07-23  0:02 ` dpdklab
2024-07-23  0:06 ` dpdklab
2024-07-23  0:08 ` |SUCCESS| " dpdklab
2024-07-23  0:10 ` |PENDING| " dpdklab
2024-07-23  0:12 ` dpdklab
2024-07-23  0:15 ` dpdklab
2024-07-23  0:18 ` dpdklab
2024-07-23  0:19 ` dpdklab
2024-07-23  0:29 ` dpdklab
2024-07-23  0:32 ` dpdklab
2024-07-23  0:32 ` dpdklab
2024-07-23  0:34 ` dpdklab
2024-07-23  0:36 ` dpdklab
2024-07-23  0:37 ` dpdklab
2024-07-23  0:39 ` dpdklab
2024-07-23  0:43 ` |SUCCESS| " dpdklab
2024-07-23  1:36 ` |PENDING| " dpdklab
2024-07-23  1:44 ` dpdklab
2024-07-23  2:01 ` dpdklab
2024-07-23  2:07 ` |SUCCESS| " dpdklab
2024-07-23  2:13 ` dpdklab
2024-07-23  2:24 ` |PENDING| " dpdklab
2024-07-23  2:26 ` dpdklab
2024-07-23  2:40 ` dpdklab
2024-07-23  2:41 ` dpdklab
2024-07-23  2:44 ` dpdklab
2024-07-23  2:47 ` dpdklab
2024-07-23  2:48 ` dpdklab
2024-07-23  2:49 ` dpdklab
2024-07-23  2:49 ` dpdklab
2024-07-23  2:55 ` dpdklab
2024-07-23  2:56 ` dpdklab
2024-07-23  3:03 ` dpdklab
2024-07-23  3:13 ` dpdklab
2024-07-23  3:18 ` dpdklab
2024-07-23  3:19 ` dpdklab
2024-07-23  3:20 ` |SUCCESS| " dpdklab
2024-07-23  3:21 ` |PENDING| " dpdklab
2024-07-23  3:21 ` dpdklab
2024-07-23  3:21 ` dpdklab
2024-07-23  3:23 ` dpdklab
2024-07-23  3:24 ` dpdklab
2024-07-23  3:25 ` |SUCCESS| " dpdklab
2024-07-23  3:25 ` |PENDING| " dpdklab
2024-07-23  3:29 ` dpdklab
2024-07-23  3:30 ` dpdklab
2024-07-23  3:31 ` dpdklab
2024-07-23  3:32 ` dpdklab
2024-07-23  3:33 ` dpdklab
2024-07-23  3:37 ` dpdklab
2024-07-23  3:39 ` dpdklab
2024-07-23  3:40 ` dpdklab
2024-07-23  3:41 ` dpdklab
2024-07-23  3:41 ` dpdklab
2024-07-23  3:41 ` dpdklab
2024-07-23  3:43 ` dpdklab
2024-07-23  3:53 ` dpdklab
2024-07-23  3:54 ` dpdklab
2024-07-23  3:55 ` |SUCCESS| " dpdklab
2024-07-23  3:56 ` |PENDING| " dpdklab
2024-07-23  3:58 ` dpdklab
2024-07-23  4:00 ` dpdklab
2024-07-23  4:02 ` dpdklab
2024-07-23  4:02 ` dpdklab
2024-07-23  4:04 ` |SUCCESS| " dpdklab
2024-07-23  4:05 ` |PENDING| " dpdklab
2024-07-23  4:10 ` dpdklab
2024-07-23  4:10 ` dpdklab
2024-07-23  4:12 ` dpdklab
2024-07-23  4:14 ` dpdklab
2024-07-23  4:15 ` dpdklab
2024-07-23  4:15 ` dpdklab
2024-07-23  4:16 ` dpdklab
2024-07-23  4:16 ` dpdklab
2024-07-23  4:17 ` |SUCCESS| " dpdklab
2024-07-23  4:20 ` |PENDING| " dpdklab
2024-07-23  4:20 ` dpdklab
2024-07-23  4:21 ` dpdklab
2024-07-23  4:22 ` dpdklab
2024-07-23  4:22 ` dpdklab
2024-07-23  4:23 ` dpdklab
2024-07-23  4:23 ` dpdklab
2024-07-23  4:24 ` dpdklab
2024-07-23  4:25 ` dpdklab
2024-07-23  4:26 ` dpdklab
2024-07-23  4:26 ` dpdklab
2024-07-23  4:26 ` dpdklab
2024-07-23  4:28 ` dpdklab
2024-07-23  4:29 ` dpdklab
2024-07-23  4:29 ` |SUCCESS| " dpdklab
2024-07-23  4:30 ` |PENDING| " dpdklab
2024-07-23  4:31 ` dpdklab
2024-07-23  4:33 ` dpdklab
2024-07-23  4:34 ` dpdklab
2024-07-23  4:36 ` dpdklab
2024-07-23  4:37 ` dpdklab
2024-07-23  4:38 ` dpdklab
2024-07-23  4:40 ` dpdklab
2024-07-23  4:58 ` dpdklab
2024-07-23  5:07 ` |SUCCESS| " dpdklab
2024-07-23  5:07 ` dpdklab
2024-07-23 22:18 ` 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=669ee5e1.050a0220.7f616.9bebSMTPIN_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).