automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: liwencheng@phytium.com.cn, robot@bytheb.org
Subject: |FAILURE| pw152815 [PATCH v6 3/3] net/macb: add necessary docs and update related files
Date: Tue,  8 Apr 2025 03:22:53 -0400	[thread overview]
Message-ID: <20250408072253.2560981-1-robot@bytheb.org> (raw)
In-Reply-To: <1744093356-313809-1-git-send-email-liwencheng@phytium.com.cn>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/14326911622
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
####################################################################################
^[[36;1m[ -z "$failed" ]^[[0m
shell: /usr/bin/bash --noprofile --norc -exo pipefail {0}
env:
  REF_GIT_BRANCH: main
  REF_GIT_REPO: https://github.com/DPDK/dpdk
  REF_GIT_TAG: v25.03
##[endgroup]
+ git remote add upstream https://github.com/DPDK/dpdk
+ git fetch upstream main
From https://github.com/DPDK/dpdk
 * branch                  main       -> FETCH_HEAD
 * [new branch]            main       -> upstream/main
+ failed=
+ devtools/check-doc-vs-code.sh upstream/main
rte_flow doc out of sync for macb
	item eth
	item ipv4
	item ipv6
	item raw
	item tcp
	item udp
+ failed=true
+ devtools/check-meson.py
+ '[' -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-04-08  7:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1744093356-313809-1-git-send-email-liwencheng@phytium.com.cn>
2025-04-08  5:53 ` |SUCCESS| pw152813-152815 " qemudev
2025-04-08  5:57 ` qemudev
2025-04-08  6:24 ` |SUCCESS| pw152815 " checkpatch
2025-04-08  7:22 ` 0-day Robot [this message]
2025-04-08 21:54 ` |SUCCESS| pw152813-152815 [PATCH] [v6,3/3] net/macb: add necessary d dpdklab
2025-04-08 22:07 ` dpdklab
2025-04-08 22:09 ` dpdklab
2025-04-08 22:12 ` dpdklab
2025-04-08 22:35 ` dpdklab
2025-04-08 22:37 ` |PENDING| " dpdklab
2025-04-08 22:50 ` |SUCCESS| " dpdklab
2025-04-08 23:03 ` dpdklab
2025-04-08 23:16 ` |PENDING| " dpdklab
2025-04-08 23:17 ` dpdklab
2025-04-08 23:24 ` |SUCCESS| " dpdklab
2025-04-08 23:31 ` dpdklab
2025-04-08 23:46 ` dpdklab
2025-04-08 23:51 ` |PENDING| " dpdklab
2025-04-08 23:57 ` |SUCCESS| " dpdklab
2025-04-09  0:05 ` dpdklab
2025-04-09  0:57 ` dpdklab
2025-04-09  1:18 ` dpdklab
2025-04-09  1:21 ` dpdklab
2025-04-09  1:32 ` dpdklab
2025-04-09  1:43 ` dpdklab
2025-04-09  1:54 ` dpdklab
2025-04-09  2:19 ` dpdklab
2025-04-10 23:30 ` dpdklab
2025-04-10 23:31 ` 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=20250408072253.2560981-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=liwencheng@phytium.com.cn \
    --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).