automatic DPDK test reports
 help / color / mirror / Atom feed
From: al-sw-devops@alabs.net
To: test-report@dpdk.org, atrwajee@amazon.com
Subject: |FAILURE| pw154631-154631 net/iavf: fix VLAN offload strip flag
Date: Mon, 23 Jun 2025 21:26:10 +0300 (IDT)	[thread overview]
Message-ID: <1466295714.8189.1750703170949@ip-10-159-234-77.eu-west-1.compute.internal> (raw)

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

Test-Name: DPDK Fast test suite
Test-Label: aws-unit-testing
Test-Status: FAILURE
_Unit Testing FAILURE_
http://dpdk.org/patch/154631

Test Status Summary:

+--------------+------------------+
| Architecture | DPDK Unit Test   |
+--------------+------------------+
| x86_64       | FAILURE           |
+--------------+------------------+
| arm64        | FAILURE           |
+--------------+------------------+


Test environment (aarch64):
Description: FAILURE
OS : Ubuntu 24.04.1 LTS
Kernel : 6.8.0-1024-aws
NIC : Elastic Network Adapter
GCC : 13.3.0-6ubuntu2~24.04

Test last 100 lines (aarch64)
Patchset range: 154631-154631

Patchset name: 

Description: FAILURE

Distro name: Ubuntu 24.04.1 LTS

Kernel: 6.8.0-1024-aws

GCC: 13.3.0-6ubuntu2~24.04

Architecture: aarch64

Processing Status: FAILURE

Full log:



Test environment (x86_64):
Description: FAILURE
OS : Ubuntu 24.04.1 LTS
Kernel : 6.8.0-1024-aws
NIC : Elastic Network Adapter
GCC : 13.3.0-6ubuntu2~24.04

Test last 100 lines (x86_64)
Patchset range: 154631-154631

Patchset name: net/iavf: fix VLAN offload strip flag

Description: FAILURE

Distro name: Ubuntu 24.04.1 LTS

Kernel: 6.8.0-1024-aws

GCC: 13.3.0-6ubuntu2~24.04

Architecture: x86_64

Processing Status: FAILURE

Full log:

                 reply	other threads:[~2025-06-23 18:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1466295714.8189.1750703170949@ip-10-159-234-77.eu-west-1.compute.internal \
    --to=al-sw-devops@alabs.net \
    --cc=atrwajee@amazon.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).