automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Lijuan Tu <lijuan.tu@intel.com>,
	Test Report <test-report@dpdk.org>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Georgii Tkachuk <georgii.tkachuk@intel.com>,
	Qian Xu <qian.q.xu@intel.com>
Cc: dpdk-test-reports@iol.unh.edu, Robin Jarry <rjarry@redhat.com>
Subject: |FAILURE| pw151959 [PATCH] net: fix IPv4 compat and mapped checks
Date: Mon, 24 Feb 2025 11:05:34 -0800 (PST)	[thread overview]
Message-ID: <67bcc2fe.170a0220.125f9e.64ceSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250224144725.271975-2-rjarry@redhat.com>

Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/151959

_Functional Testing issues_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Monday, February 24 2025 14:47:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa

151959 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#214162

Test environment and result as below:

Ubuntu 24.04 LTS
Kernel: 6.8.0-44-generic
Compiler: gcc 13.2.0
NIC: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ 40 Mbps

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| mac_filter |  FAIL  |
+------------+--------+


Ubuntu 22.04
Kernel: 5.15.0-131-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.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  |
+-----------------------------+--------+


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  |
+-----------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-02-24 19:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250224144725.271975-2-rjarry@redhat.com>
2025-02-24 14:13 ` |SUCCESS| pw151959 [PATCH dpdk] " qemudev
2025-02-24 14:17 ` qemudev
2025-02-24 14:47 ` checkpatch
2025-02-24 16:04 ` 0-day Robot
2025-02-24 19:05 ` dpdklab [this message]
2025-02-24 19:06 ` |FAILURE| pw151959 [PATCH] " dpdklab
2025-02-24 19:24 ` |SUCCESS| " dpdklab
2025-02-24 19:53 ` |PENDING| " dpdklab
2025-02-24 19:58 ` |SUCCESS| " dpdklab
2025-02-24 22:29 ` dpdklab
2025-02-24 22:47 ` 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=67bcc2fe.170a0220.125f9e.64ceSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@intel.com \
    --cc=georgii.tkachuk@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=rjarry@redhat.com \
    --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).