From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: venkatx.sivaramakrishnan@intel.com, robot@bytheb.org
Subject: |FAILURE| pw137097 [PATCH v4 2/2] doc: remove outdated version details
Date: Fri, 23 Feb 2024 08:24:50 -0500 [thread overview]
Message-ID: <20240223132450.1903016-1-robot@bytheb.org> (raw)
In-Reply-To: <20240223122908.3589264-2-venkatx.sivaramakrishnan@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/137097/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8019399344
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) variable
Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (89 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed (1 filtered out), 0 Changed (49 filtered out), 0 Added (10 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (39 filtered out), 0 Added (6 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added (2 filtered out) variables
Functions changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed, 0 Added (2 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2024-02-23 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240223122908.3589264-2-venkatx.sivaramakrishnan@intel.com>
2024-02-23 12:06 ` |SUCCESS| pw137096-137097 " qemudev
2024-02-23 12:10 ` qemudev
2024-02-23 12:29 ` |SUCCESS| pw137097 " checkpatch
2024-02-23 13:24 ` 0-day Robot [this message]
2024-02-28 18:09 ` |SUCCESS| pw137096-137097 [PATCH] [v4,2/2] doc: remove outdated vers dpdklab
2024-02-28 18:10 ` dpdklab
2024-02-28 18:24 ` 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=20240223132450.1903016-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.org \
--cc=venkatx.sivaramakrishnan@intel.com \
/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).