automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: wff_light@vip.163.com, robot@bytheb.org
Subject: |FAILURE| pw154686 [V2 18/18] drivers/net: add hinic3 PMD build and doc files
Date: Tue, 24 Jun 2025 23:43:31 -0400	[thread overview]
Message-ID: <20250625034331.447253-1-robot@bytheb.org> (raw)
In-Reply-To: <20250625022827.3091-19-wff_light@vip.163.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15866104937
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 mpls
	item nsh
	item nvgre
	item pf
	item phy_port
	item port_id
	item pppoe_proto_id
	item pppoed
	item pppoes
	item raw
	item sctp
	item tag
	item tcp
	item udp
	item vf
	item vlan
	item vxlan
	item vxlan_gpe
	action queue
+ failed=true
+ devtools/check-meson.py
+ devtools/check-spdx-tag.sh
total: 0 missing SPDX, 0 license errors, 0 warnings
+ '[' -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-06-25  3:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250625022827.3091-19-wff_light@vip.163.com>
2025-06-25  2:03 ` |SUCCESS| pw154672-154686 " qemudev
2025-06-25  2:08 ` qemudev
2025-06-25  2:33 ` |SUCCESS| pw154686 " checkpatch
2025-06-25  3:43 ` 0-day Robot [this message]
2025-06-25  5:16 ` |SUCCESS| pw154672-154686 [PATCH] [V2,18/18] drivers/net: add hinic3 dpdklab
2025-06-25  5:47 ` dpdklab
2025-06-25  6:04 ` dpdklab
2025-06-25  6:30 ` dpdklab
2025-06-25  6:38 ` |FAILURE| " dpdklab
2025-06-25  6:41 ` |SUCCESS| " dpdklab
2025-06-25  6:47 ` |FAILURE| " dpdklab
2025-06-25  6:52 ` |SUCCESS| " dpdklab
2025-06-25  7:13 ` |FAILURE| " dpdklab
2025-06-25  7:17 ` dpdklab
2025-06-25  7:26 ` |SUCCESS| " dpdklab
2025-06-25  7:32 ` dpdklab
2025-06-25  8:06 ` dpdklab
2025-06-25  8:07 ` dpdklab
2025-06-25  8:07 ` dpdklab
2025-06-25  8:07 ` dpdklab
2025-06-25  8:08 ` dpdklab
2025-06-25  8:08 ` dpdklab
2025-06-25 10:57 ` |FAILURE| " dpdklab
2025-06-25 12:31 ` |PENDING| " dpdklab
2025-06-25 12:42 ` |SUCCESS| " 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=20250625034331.447253-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=test-report@dpdk.org \
    --cc=wff_light@vip.163.com \
    /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).