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| pw159585 [PATCH] [v2] bpf: fix x86 call stack alignment, a
Date: Thu, 08 Jan 2026 15:12:01 -0800 (PST)	[thread overview]
Message-ID: <696039c1.050a0220.35b8e6.ccffSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260105160958.80443-1-marat.khalili@huawei.com>

Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/159585

_Functional Testing PASS_

Submitter: Marat Khalili <marat.khalili@huawei.com>
Date: Monday, January 05 2026 16:09:57 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cd60dcd503b91956f966a1f6d595b35d256ac00f

159585 --> functional testing pass

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8.0-55-generic
Compiler: gcc 13.3.0
NIC: Mellanox ConnectX-5 100000 Mbps

Aggregate Results by Test Suite
+---------------------------------+--------+
|           Test Suite            | Result |
+=================================+========+
| blocklist                       |  PASS  |
+---------------------------------+--------+
| promisc_support                 |  PASS  |
+---------------------------------+--------+
| uni_pkt                         |  PASS  |
+---------------------------------+--------+
| hello_world                     |  PASS  |
+---------------------------------+--------+
| l2fwd                           |  PASS  |
+---------------------------------+--------+
| port_restart_config_persistency |  PASS  |
+---------------------------------+--------+
| packet_capture                  |  PASS  |
+---------------------------------+--------+
| softnic                         |  PASS  |
+---------------------------------+--------+
| vlan                            |  PASS  |
+---------------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2026-01-08 23:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260105160958.80443-1-marat.khalili@huawei.com>
2026-01-05 16:01 ` |SUCCESS| pw159585 [PATCH v2] bpf: fix x86 call stack alignment, add tests qemudev
2026-01-05 16:06 ` qemudev
2026-01-05 16:11 ` checkpatch
2026-01-05 18:07 ` 0-day Robot
2026-01-05 18:07 ` 0-day Robot
2026-01-07 21:08 ` |SUCCESS| pw159585 [PATCH] [v2] bpf: fix x86 call stack alignment, a dpdklab
2026-01-08  1:05 ` dpdklab
2026-01-08  2:14 ` dpdklab
2026-01-08  5:51 ` |PENDING| " dpdklab
2026-01-08  6:41 ` |SUCCESS| " dpdklab
2026-01-08 13:03 ` dpdklab
2026-01-08 19:59 ` dpdklab
2026-01-08 19:59 ` dpdklab
2026-01-08 22:33 ` dpdklab
2026-01-08 22:38 ` dpdklab
2026-01-08 22:51 ` dpdklab
2026-01-08 22:51 ` dpdklab
2026-01-08 23:06 ` dpdklab
2026-01-08 23:10 ` dpdklab
2026-01-08 23:12 ` dpdklab [this message]
2026-01-08 23:46 ` dpdklab
2026-01-08 23:51 ` dpdklab
2026-01-08 23:52 ` dpdklab
2026-01-08 23:53 ` dpdklab
2026-01-08 23:53 ` dpdklab
2026-01-09 14:32 ` 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=696039c1.050a0220.35b8e6.ccffSMTPIN_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).