From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: g.singh@nxp.com, robot@bytheb.org
Subject: |FAILURE| pw153949 [PATCH v2 11/11] net/dpaa2: enable software taildrop for ordered queues
Date: Mon, 2 Jun 2025 07:48:48 -0400 [thread overview]
Message-ID: <20250602114848.239267-1-robot@bytheb.org> (raw)
In-Reply-To: <20250602104041.3322164-12-g.singh@nxp.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/153949/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/15390504587
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;1mdevtools/check-doc-vs-code.sh upstream/main || failed=true^[[0m
^[[36;1mdevtools/check-meson.py || failed=true^[[0m
^[[36;1mdevtools/check-spdx-tag.sh || failed=true^[[0m
^[[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
+ devtools/check-meson.py
+ devtools/check-spdx-tag.sh
drivers/net/dpaa2/mc/fsl_dpmac.h
drivers/net/dpaa2/mc/fsl_dpmac.h
total: 1 missing SPDX, 0 license errors, 1 warnings
+ failed=true
+ '[' -z true ']'
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "Check patches" at step Check patches
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2025-06-02 11:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250602104041.3322164-12-g.singh@nxp.com>
2025-06-02 10:07 ` |SUCCESS| pw153939-153949 " qemudev
2025-06-02 10:12 ` qemudev
2025-06-02 10:42 ` |SUCCESS| pw153949 " checkpatch
2025-06-02 11:48 ` 0-day Robot [this message]
2025-06-02 14:15 ` |SUCCESS| pw153939-153949 [PATCH] [v2,11/11] net/dpaa2: enable softw dpdklab
2025-06-02 14:24 ` dpdklab
2025-06-02 14:46 ` |PENDING| " dpdklab
2025-06-02 15:20 ` dpdklab
2025-06-02 15:28 ` dpdklab
2025-06-02 15:45 ` |SUCCESS| " dpdklab
2025-06-02 16:09 ` dpdklab
2025-06-02 16:20 ` dpdklab
2025-06-02 16:43 ` dpdklab
2025-06-02 16:56 ` |WARNING| " dpdklab
2025-06-02 17:27 ` dpdklab
2025-06-02 17:53 ` |SUCCESS| " dpdklab
2025-06-02 19:01 ` dpdklab
2025-06-04 22:05 ` dpdklab
2025-06-06 0:18 ` |WARNING| " 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=20250602114848.239267-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=g.singh@nxp.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).