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| pw142759-142760 [PATCH] [v2,2/2] examples/l3fwd: fix read
Date: Tue, 30 Jul 2024 10:18:51 -0700 (PDT)	[thread overview]
Message-ID: <66a9207b.170a0220.8e9d8.9495SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240730122235.1084-3-konstantin.v.ananyev@yandex.ru>

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

_Functional Testing PASS_

Submitter: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Date: Tuesday, July 30 2024 12:22:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4b5abe7ec1ed2d43a285599bbba23f62ac049d8f

142759-142760 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#171702

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

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-30 17:47 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240730122235.1084-3-konstantin.v.ananyev@yandex.ru>
2024-07-30 13:34 ` |SUCCESS| pw142759-142760 [PATCH v2 2/2] examples/l3fwd: fix read beyond array boundaries in ACL mode qemudev
2024-07-30 13:39 ` qemudev
2024-07-30 13:58 ` |WARNING| pw142760 " checkpatch
2024-07-30 15:02 ` |SUCCESS| " 0-day Robot
2024-07-30 16:49 ` |SUCCESS| pw142759-142760 [PATCH] [v2,2/2] examples/l3fwd: fix read dpdklab
2024-07-30 17:03 ` |PENDING| " dpdklab
2024-07-30 17:05 ` dpdklab
2024-07-30 17:11 ` |SUCCESS| " dpdklab
2024-07-30 17:13 ` dpdklab
2024-07-30 17:15 ` |PENDING| " dpdklab
2024-07-30 17:18 ` dpdklab [this message]
2024-07-30 17:22 ` dpdklab
2024-07-30 17:25 ` |SUCCESS| " dpdklab
2024-07-30 17:26 ` dpdklab
2024-07-30 17:28 ` |PENDING| " dpdklab
2024-07-30 17:29 ` dpdklab
2024-07-30 17:33 ` dpdklab
2024-07-30 17:35 ` dpdklab
2024-07-30 17:36 ` |SUCCESS| " dpdklab
2024-07-30 17:38 ` |PENDING| " dpdklab
2024-07-30 17:42 ` dpdklab
2024-07-30 17:48 ` dpdklab
2024-07-30 17:49 ` dpdklab
2024-07-30 17:50 ` dpdklab
2024-07-30 17:52 ` dpdklab
2024-07-30 17:55 ` dpdklab
2024-07-30 17:56 ` dpdklab
2024-07-30 17:57 ` |SUCCESS| " dpdklab
2024-07-30 18:02 ` dpdklab
2024-07-30 18:02 ` dpdklab
2024-07-30 18:05 ` |PENDING| " dpdklab
2024-07-30 18:07 ` |SUCCESS| " dpdklab
2024-07-30 18:12 ` dpdklab
2024-07-30 18:19 ` dpdklab
2024-07-30 18:31 ` dpdklab
2024-07-30 18:53 ` |PENDING| " dpdklab
2024-07-30 19:01 ` dpdklab
2024-07-30 19:04 ` dpdklab
2024-07-30 19:06 ` dpdklab
2024-07-30 19:07 ` dpdklab
2024-07-30 19:09 ` dpdklab
2024-07-30 19:09 ` dpdklab
2024-07-30 19:10 ` dpdklab
2024-07-30 19:10 ` dpdklab
2024-07-30 19:17 ` |SUCCESS| " dpdklab
2024-07-30 19:17 ` |PENDING| " dpdklab
2024-07-30 19:18 ` dpdklab
2024-07-30 19:18 ` dpdklab
2024-07-30 19:22 ` dpdklab
2024-07-30 19:25 ` dpdklab
2024-07-30 19:30 ` dpdklab
2024-07-30 19:30 ` dpdklab
2024-07-30 19:34 ` dpdklab
2024-07-30 19:37 ` dpdklab
2024-07-30 19:45 ` dpdklab
2024-07-30 19:45 ` dpdklab
2024-07-30 19:46 ` dpdklab
2024-07-30 19:50 ` dpdklab
2024-07-30 19:54 ` dpdklab
2024-07-30 19:54 ` |SUCCESS| " dpdklab
2024-07-30 19:56 ` |PENDING| " dpdklab
2024-07-30 19:58 ` dpdklab
2024-07-30 20:02 ` dpdklab
2024-07-30 20:02 ` dpdklab
2024-07-30 20:02 ` dpdklab
2024-07-30 20:07 ` dpdklab
2024-07-30 20:08 ` dpdklab
2024-07-30 20:09 ` dpdklab
2024-07-30 20:09 ` dpdklab
2024-07-30 20:09 ` dpdklab
2024-07-30 20:12 ` dpdklab
2024-07-30 20:12 ` dpdklab
2024-07-30 20:15 ` dpdklab
2024-07-30 20:27 ` dpdklab
2024-07-30 20:50 ` dpdklab
2024-07-30 20:50 ` dpdklab
2024-07-30 20:52 ` dpdklab
2024-07-30 20:54 ` dpdklab
2024-07-30 20:55 ` dpdklab
2024-07-30 20:56 ` dpdklab
2024-07-30 20:59 ` dpdklab
2024-07-30 21:00 ` dpdklab
2024-07-30 21:02 ` dpdklab
2024-07-30 21:03 ` dpdklab
2024-07-30 21:03 ` dpdklab
2024-07-30 21:06 ` dpdklab
2024-07-30 21:07 ` |SUCCESS| " dpdklab
2024-07-30 21:08 ` |PENDING| " dpdklab
2024-07-30 21:08 ` dpdklab
2024-07-30 21:10 ` dpdklab
2024-07-30 21:11 ` dpdklab
2024-07-30 21:12 ` dpdklab
2024-07-30 21:14 ` dpdklab
2024-07-30 21:14 ` dpdklab
2024-07-30 21:14 ` dpdklab
2024-07-30 21:16 ` dpdklab
2024-07-30 21:18 ` dpdklab
2024-07-30 21:19 ` dpdklab
2024-07-30 21:24 ` dpdklab
2024-07-30 21:25 ` dpdklab
2024-07-30 21:26 ` dpdklab
2024-07-30 21:26 ` dpdklab
2024-07-30 21:27 ` dpdklab
2024-07-30 21:28 ` dpdklab
2024-07-30 21:29 ` dpdklab
2024-07-30 21:30 ` dpdklab
2024-07-30 21:31 ` dpdklab
2024-07-30 21:34 ` dpdklab
2024-07-30 21:36 ` |SUCCESS| " dpdklab
2024-07-30 21:36 ` |PENDING| " dpdklab
2024-07-30 21:37 ` dpdklab
2024-07-30 21:37 ` |SUCCESS| " dpdklab
2024-07-30 21:40 ` |PENDING| " dpdklab
2024-07-30 21:52 ` |SUCCESS| " dpdklab
2024-07-30 22:07 ` dpdklab
2024-07-31  1:34 ` 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=66a9207b.170a0220.8e9d8.9495SMTPIN_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).