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| pw143011-143013 [PATCH] [3/3] net/enic: allow multicast in
Date: Wed, 07 Aug 2024 23:48:35 -0700 (PDT)	[thread overview]
Message-ID: <66b46a43.170a0220.3b24b7.1aafSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240808041838.31367-4-hyonkim@cisco.com>

Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143013

_Functional Testing PASS_

Submitter: Hyong Youb Kim <hyonkim@cisco.com>
Date: Thursday, August 08 2024 04:18:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2155f1f2054aa06f0b58e9ade9babf1f0a97a410

143011-143013 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#173656

Test environment and result as below:

Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| cmdline         |  PASS  |
+-----------------+--------+
| coremask        |  PASS  |
+-----------------+--------+
| ipv4_reassembly |  PASS  |
+-----------------+--------+
| l2fwd           |  PASS  |
+-----------------+--------+
| rxtx_callbacks  |  PASS  |
+-----------------+--------+
| tso             |  PASS  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-08  6:48 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240808041838.31367-4-hyonkim@cisco.com>
2024-08-08  3:52 ` |SUCCESS| pw143011-143013 [PATCH 3/3] net/enic: allow multicast in MAC address add callback qemudev
2024-08-08  3:56 ` qemudev
2024-08-08  4:19 ` |SUCCESS| pw143013 " checkpatch
2024-08-08  5:23 ` |FAILURE| " 0-day Robot
2024-08-08  5:34 ` |SUCCESS| pw143011-143013 [PATCH] [3/3] net/enic: allow multicast in dpdklab
2024-08-08  5:49 ` |PENDING| " dpdklab
2024-08-08  5:50 ` dpdklab
2024-08-08  5:50 ` |SUCCESS| " dpdklab
2024-08-08  5:59 ` dpdklab
2024-08-08  6:03 ` dpdklab
2024-08-08  6:03 ` dpdklab
2024-08-08  6:07 ` |PENDING| " dpdklab
2024-08-08  6:09 ` dpdklab
2024-08-08  6:13 ` |SUCCESS| " dpdklab
2024-08-08  6:13 ` |PENDING| " dpdklab
2024-08-08  6:13 ` dpdklab
2024-08-08  6:14 ` dpdklab
2024-08-08  6:16 ` |SUCCESS| " dpdklab
2024-08-08  6:16 ` |PENDING| " dpdklab
2024-08-08  6:17 ` dpdklab
2024-08-08  6:17 ` dpdklab
2024-08-08  6:24 ` dpdklab
2024-08-08  6:27 ` dpdklab
2024-08-08  6:40 ` dpdklab
2024-08-08  6:40 ` dpdklab
2024-08-08  6:42 ` |FAILURE| " dpdklab
2024-08-08  6:43 ` |PENDING| " dpdklab
2024-08-08  6:43 ` |FAILURE| " dpdklab
2024-08-08  6:45 ` dpdklab
2024-08-08  6:45 ` |PENDING| " dpdklab
2024-08-08  6:48 ` dpdklab [this message]
2024-08-08  6:49 ` |FAILURE| " dpdklab
2024-08-08  6:49 ` |PENDING| " dpdklab
2024-08-08  6:49 ` |FAILURE| " dpdklab
2024-08-08  6:50 ` dpdklab
2024-08-08  6:50 ` dpdklab
2024-08-08  6:50 ` |PENDING| " dpdklab
2024-08-08  6:51 ` dpdklab
2024-08-08  6:52 ` |SUCCESS| " dpdklab
2024-08-08  6:53 ` |PENDING| " dpdklab
2024-08-08  6:53 ` dpdklab
2024-08-08  6:54 ` dpdklab
2024-08-08  6:54 ` dpdklab
2024-08-08  6:56 ` dpdklab
2024-08-08  6:57 ` dpdklab
2024-08-08  6:58 ` dpdklab
2024-08-08  6:59 ` dpdklab
2024-08-08  7:00 ` dpdklab
2024-08-08  7:00 ` dpdklab
2024-08-08  7:03 ` dpdklab
2024-08-08  7:04 ` dpdklab
2024-08-08  7:06 ` dpdklab
2024-08-08  7:07 ` |SUCCESS| " dpdklab
2024-08-08  7:07 ` |PENDING| " dpdklab
2024-08-08  7:08 ` dpdklab
2024-08-08  7:09 ` dpdklab
2024-08-08  7:10 ` |FAILURE| " dpdklab
2024-08-08  7:11 ` |PENDING| " dpdklab
2024-08-08  7:13 ` |FAILURE| " dpdklab
2024-08-08  7:14 ` dpdklab
2024-08-08  7:16 ` dpdklab
2024-08-08  7:19 ` dpdklab
2024-08-08  7:21 ` dpdklab
2024-08-08  7:22 ` dpdklab
2024-08-08  7:22 ` dpdklab
2024-08-08  7:24 ` dpdklab
2024-08-08  7:26 ` dpdklab
2024-08-08  7:29 ` dpdklab
2024-08-08  7:29 ` dpdklab
2024-08-08  7:31 ` |WARNING| " dpdklab
2024-08-08  7:35 ` |FAILURE| " dpdklab
2024-08-08  7:42 ` |PENDING| " dpdklab
2024-08-08  8:39 ` |SUCCESS| " dpdklab
2024-08-08  8:56 ` |FAILURE| " dpdklab
2024-08-08  8:58 ` dpdklab
2024-08-08  9:01 ` dpdklab
2024-08-08  9:04 ` dpdklab
2024-08-08  9:07 ` dpdklab
2024-08-08  9:09 ` |SUCCESS| " dpdklab
2024-08-08  9:13 ` |FAILURE| " dpdklab
2024-08-08  9:15 ` dpdklab
2024-08-08  9:15 ` dpdklab
2024-08-08  9:15 ` |SUCCESS| " dpdklab
2024-08-08  9:17 ` |FAILURE| " dpdklab
2024-08-08  9:17 ` dpdklab
2024-08-08  9:18 ` dpdklab
2024-08-08  9:19 ` dpdklab
2024-08-08  9:19 ` dpdklab
2024-08-08  9:20 ` |PENDING| " dpdklab
2024-08-08  9:21 ` |FAILURE| " dpdklab
2024-08-08  9:21 ` |PENDING| " dpdklab
2024-08-08  9:21 ` |FAILURE| " dpdklab
2024-08-08  9:22 ` dpdklab
2024-08-08  9:24 ` |PENDING| " dpdklab
2024-08-08  9:24 ` |FAILURE| " dpdklab
2024-08-08  9:25 ` |PENDING| " dpdklab
2024-08-08  9:25 ` dpdklab
2024-08-08  9:25 ` |WARNING| " dpdklab
2024-08-08  9:28 ` |FAILURE| " dpdklab
2024-08-08  9:29 ` dpdklab
2024-08-08  9:29 ` dpdklab
2024-08-08  9:30 ` dpdklab
2024-08-08  9:33 ` dpdklab
2024-08-08  9:33 ` dpdklab
2024-08-08  9:35 ` |SUCCESS| " dpdklab
2024-08-08  9:36 ` |FAILURE| " dpdklab
2024-08-08  9:37 ` dpdklab
2024-08-08  9:37 ` dpdklab
2024-08-08  9:38 ` dpdklab
2024-08-08  9:40 ` |WARNING| " dpdklab
2024-08-08  9:40 ` dpdklab
2024-08-08  9:41 ` dpdklab
2024-08-08  9:47 ` |SUCCESS| " dpdklab
2024-08-08 10:03 ` 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=66b46a43.170a0220.3b24b7.1aafSMTPIN_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).