automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: liujie5@linkdatatechnology.com, robot@bytheb.org
Subject: |FAILURE| pw155256 [PATCH v9 14/14] net/sxe: add Solve compilation problems.
Date: Wed, 16 Jul 2025 05:43:20 -0400	[thread overview]
Message-ID: <20250716094320.2381942-1-robot@bytheb.org> (raw)
In-Reply-To: <20250716082930.83026-14-liujie5@linkdatatechnology.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/155256/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/16314825601
Build Logs:
-----------------------Summary of failed steps-----------------------
"Check patches" failed at step Check patches
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "Check patches" at step Check patches
####################################################################################
	item fuzzy
	item ipv4
	item ipv6
	item nvgre
	item raw
	item sctp
	item tcp
	item udp
	item vlan
	item vxlan
	action drop
	action mark
	action pf
	action queue
	action rss
	action security
	action vf
+ failed=true
+ devtools/check-meson.py
+ devtools/check-spdx-tag.sh
drivers/net/sxe/rte_pmd_sxe_version.map
total: 1 missing SPDX, 0 license errors, 0 warnings
+ failed=true
+ '[' -z true ']'
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "Check patches" at step Check patches
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-07-16  9:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250716082930.83026-14-liujie5@linkdatatechnology.com>
2025-07-16  7:58 ` |SUCCESS| pw155243-155256 " qemudev
2025-07-16  8:03 ` qemudev
2025-07-16  8:35 ` |WARNING| pw155256 " checkpatch
2025-07-16  9:16 ` |PENDING| pw155243-155256 [PATCH] [v9,14/14] net/sxe: add Solve comp dpdklab
2025-07-16  9:21 ` |SUCCESS| " dpdklab
2025-07-16  9:23 ` |PENDING| " dpdklab
2025-07-16  9:27 ` dpdklab
2025-07-16  9:30 ` |SUCCESS| " dpdklab
2025-07-16  9:33 ` dpdklab
2025-07-16  9:36 ` dpdklab
2025-07-16  9:36 ` dpdklab
2025-07-16  9:37 ` dpdklab
2025-07-16  9:39 ` |PENDING| " dpdklab
2025-07-16  9:43 ` 0-day Robot [this message]
2025-07-16 10:15 ` |SUCCESS| " dpdklab
2025-07-16 10:15 ` dpdklab
2025-07-16 10:27 ` dpdklab
2025-07-16 10:28 ` dpdklab
2025-07-16 10:31 ` dpdklab
2025-07-16 10:45 ` dpdklab
2025-07-16 12:56 ` dpdklab
2025-07-16 12:59 ` dpdklab
2025-07-16 15:17 ` 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=20250716094320.2381942-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=liujie5@linkdatatechnology.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).