From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: liwencheng@phytium.com.cn, robot@bytheb.org
Subject: |FAILURE| pw149068 [PATCH v3 3/3] net/macb: fix logic error in macb_rxq_rearm function
Date: Fri, 6 Dec 2024 04:22:17 -0500 [thread overview]
Message-ID: <20241206092217.1624345-1-robot@bytheb.org> (raw)
In-Reply-To: <1733472580-314516-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/149068/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/12195421420
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 ipv6
item raw
item tcp
item udp
+ failed=true
+ devtools/check-meson.py
Error: Incorrect indent at drivers/net/macb/meson.build:14
Error: Incorrect indent at drivers/net/macb/meson.build:15
Error parsing drivers/net/macb/base/meson.build:4, got some tabulation
Error: Incorrect indent at drivers/net/macb/base/meson.build:5
Error parsing drivers/net/macb/base/meson.build:5, got some tabulation
Error: Incorrect indent at drivers/net/macb/base/meson.build:6
Error parsing drivers/net/macb/base/meson.build:6, got some tabulation
Error: Incorrect indent at drivers/net/macb/base/meson.build:7
Error parsing drivers/net/macb/base/meson.build:10, got some tabulation
Error parsing drivers/net/macb/base/meson.build:11, got some tabulation
Error parsing drivers/net/macb/base/meson.build:12, got some tabulation
Error parsing drivers/net/macb/base/meson.build:17, got some tabulation
Error parsing drivers/net/macb/base/meson.build:18, got some tabulation
Error parsing drivers/net/macb/base/meson.build:19, got some tabulation
Error parsing drivers/net/macb/base/meson.build:23, got some tabulation
Error parsing drivers/net/macb/base/meson.build:24, got some tabulation
+ devtools/check-symbol-maps.sh
+ '[' -z true ']'
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "Check patches" at step Check patches
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2024-12-06 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1733472580-314516-1-git-send-email-liwencheng@phytium.com.cn>
2024-12-06 7:39 ` |SUCCESS| pw149066-149068 " qemudev
2024-12-06 7:43 ` qemudev
2024-12-06 8:10 ` |WARNING| pw149068 " checkpatch
2024-12-06 8:36 ` |FAILURE| pw149066-149068 [PATCH] [v3, " dpdklab
2024-12-06 9:22 ` 0-day Robot [this message]
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=20241206092217.1624345-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).