From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: chen.bingbin@zte.com.cn, robot@bytheb.org
Subject: |FAILURE| pw151242 [PATCH v1 14/14] net/zxdh: clean stat values
Date: Sun, 9 Feb 2025 22:05:02 -0500 [thread overview]
Message-ID: <20250210030502.3291338-1-robot@bytheb.org> (raw)
In-Reply-To: <20250210015017.4105624-9-chen.bingbin@zte.com.cn>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/151242/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/13232305190
Build Logs:
-----------------------Summary of failed steps-----------------------
"fedora:39-gcc" failed at step Build
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "fedora:39-gcc" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-gcc" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2025-02-10 3:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250210015017.4105624-9-chen.bingbin@zte.com.cn>
2025-02-10 1:29 ` |SUCCESS| pw151229-151242 " qemudev
2025-02-10 1:34 ` qemudev
2025-02-10 2:04 ` |WARNING| pw151242 " checkpatch
2025-02-10 2:44 ` |SUCCESS| pw151229-151242 [PATCH] [v1,14/14] net/zxdh: clean stat va dpdklab
2025-02-10 2:44 ` dpdklab
2025-02-10 2:55 ` dpdklab
2025-02-10 2:58 ` dpdklab
2025-02-10 2:58 ` dpdklab
2025-02-10 3:00 ` |PENDING| " dpdklab
2025-02-10 3:01 ` |SUCCESS| " dpdklab
2025-02-10 3:05 ` 0-day Robot [this message]
2025-02-10 3:07 ` |FAILURE| " dpdklab
2025-02-10 3:08 ` |SUCCESS| " dpdklab
2025-02-10 3:09 ` dpdklab
2025-02-10 3:10 ` |PENDING| " dpdklab
2025-02-10 3:13 ` |SUCCESS| " dpdklab
2025-02-10 3:20 ` |FAILURE| " dpdklab
2025-02-10 3:20 ` |SUCCESS| " dpdklab
2025-02-10 3:21 ` |FAILURE| " dpdklab
2025-02-10 3:23 ` dpdklab
2025-02-10 3:23 ` |PENDING| " dpdklab
2025-02-10 3:29 ` |FAILURE| " dpdklab
2025-02-10 3:53 ` |SUCCESS| " dpdklab
2025-02-10 4:20 ` |WARNING| " dpdklab
2025-02-10 4:21 ` |SUCCESS| " dpdklab
2025-02-10 4:31 ` |WARNING| " dpdklab
2025-02-10 5:16 ` |SUCCESS| " dpdklab
2025-02-10 5:17 ` |FAILURE| " 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=20250210030502.3291338-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=chen.bingbin@zte.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).