From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: t.aliev.mnt@gmail.com, robot@bytheb.org
Subject: |FAILURE| pw155592 [PATCH] raw/ntb: immediate return if no doorbells
Date: Wed, 30 Jul 2025 05:43:59 -0400 [thread overview]
Message-ID: <20250730094359.3304512-1-robot@bytheb.org> (raw)
In-Reply-To: <20250730084440.102403-1-t.aliev.mnt@gmail.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/155592/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/16618267396
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;1mfailed=^[[0m
^[[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: none
##[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
0001-raw-ntb-immediate-return-if-no-doorbells.patch
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-----------------------------
next prev parent reply other threads:[~2025-07-30 9:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250730084440.102403-1-t.aliev.mnt@gmail.com>
2025-07-30 8:11 ` |SUCCESS| " qemudev
2025-07-30 8:15 ` qemudev
2025-07-30 8:43 ` |WARNING| " checkpatch
2025-07-30 9:25 ` |SUCCESS| " dpdklab
2025-07-30 9:26 ` dpdklab
2025-07-30 9:33 ` dpdklab
2025-07-30 9:40 ` dpdklab
2025-07-30 9:41 ` dpdklab
2025-07-30 9:42 ` dpdklab
2025-07-30 9:42 ` dpdklab
2025-07-30 9:43 ` |PENDING| " dpdklab
2025-07-30 9:43 ` 0-day Robot [this message]
2025-07-30 10:02 ` |SUCCESS| " dpdklab
2025-07-30 10:11 ` dpdklab
2025-07-30 10:15 ` dpdklab
2025-07-30 10:18 ` dpdklab
2025-07-30 10:52 ` dpdklab
2025-07-30 13:07 ` 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=20250730094359.3304512-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=t.aliev.mnt@gmail.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).