automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: abailey@iol.unh.edu, robot@bytheb.org
Subject: |FAILURE| pw156438 [PATCH v2 3/3] dts: update tx_offload test from old dts
Date: Wed,  3 Sep 2025 15:25:27 -0400	[thread overview]
Message-ID: <20250903192527.4082864-1-robot@bytheb.org> (raw)
In-Reply-To: <20250903180414.83001-4-abailey@iol.unh.edu>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/17442599428
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
dts/tests/TestSuite_rxtx_offload.py
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-----------------------------

  parent reply	other threads:[~2025-09-03 19:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250903180414.83001-4-abailey@iol.unh.edu>
2025-09-03 17:31 ` |SUCCESS| pw156436-156438 " qemudev
2025-09-03 17:36 ` qemudev
2025-09-03 18:02 ` |SUCCESS| pw156438 " checkpatch
2025-09-03 18:26 ` |FAILURE| pw156436-156438 [PATCH] [v2,3/3] dts: update tx_offload te dpdklab
2025-09-03 18:30 ` |PENDING| " dpdklab
2025-09-03 18:31 ` dpdklab
2025-09-03 18:34 ` |SUCCESS| " dpdklab
2025-09-03 18:37 ` dpdklab
2025-09-03 18:38 ` |PENDING| " dpdklab
2025-09-03 18:39 ` dpdklab
2025-09-03 18:41 ` dpdklab
2025-09-03 18:52 ` |FAILURE| " dpdklab
2025-09-03 18:52 ` |SUCCESS| " dpdklab
2025-09-03 18:54 ` dpdklab
2025-09-03 18:54 ` dpdklab
2025-09-03 18:58 ` dpdklab
2025-09-03 19:08 ` dpdklab
2025-09-03 19:08 ` dpdklab
2025-09-03 19:12 ` dpdklab
2025-09-03 19:20 ` |WARNING| " dpdklab
2025-09-03 19:25 ` 0-day Robot [this message]
2025-09-03 20:59 ` |SUCCESS| " dpdklab
2025-09-04  0:36 ` dpdklab
2025-09-05  6:52 ` 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=20250903192527.4082864-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=abailey@iol.unh.edu \
    --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).