automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: rjarry@redhat.com, robot@bytheb.org
Subject: |FAILURE| pw138850 [PATCH v5] graph: expose node context as pointers
Date: Wed, 27 Mar 2024 06:05:08 -0400	[thread overview]
Message-ID: <20240327100508.1285301-1-robot@bytheb.org> (raw)
In-Reply-To: <20240327091440.1166119-2-rjarry@redhat.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/8449469154
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, 0 Added (1 filtered out) 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, 0 Changed (3 filtered out), 0 Added functions
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 (5 filtered out), 0 Changed (290 filtered out), 0 Added (25 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 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-----------------------------

  parent reply	other threads:[~2024-03-27 10:05 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240327091440.1166119-2-rjarry@redhat.com>
2024-03-27  9:03 ` |SUCCESS| " qemudev
2024-03-27  9:08 ` qemudev
2024-03-27  9:17 ` checkpatch
2024-03-27  9:57 ` |WARNING| pw138850 [PATCH] [v5] graph: expose node context as pointe dpdklab
2024-03-27  9:58 ` |SUCCESS| " dpdklab
2024-03-27  9:58 ` dpdklab
2024-03-27  9:59 ` dpdklab
2024-03-27  9:59 ` |WARNING| " dpdklab
2024-03-27  9:59 ` dpdklab
2024-03-27  9:59 ` |SUCCESS| " dpdklab
2024-03-27  9:59 ` dpdklab
2024-03-27 10:00 ` dpdklab
2024-03-27 10:00 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-03-27 10:02 ` dpdklab
2024-03-27 10:02 ` dpdklab
2024-03-27 10:02 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:04 ` dpdklab
2024-03-27 10:04 ` |WARNING| " dpdklab
2024-03-27 10:04 ` |SUCCESS| " dpdklab
2024-03-27 10:04 ` dpdklab
2024-03-27 10:05 ` 0-day Robot [this message]
2024-03-27 10:05 ` dpdklab
2024-03-27 10:05 ` dpdklab
2024-03-27 10:05 ` dpdklab
2024-03-27 10:05 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:07 ` |WARNING| " dpdklab
2024-03-27 10:07 ` |SUCCESS| " dpdklab
2024-03-27 10:07 ` dpdklab
2024-03-27 10:08 ` dpdklab
2024-03-27 10:08 ` |WARNING| " dpdklab
2024-03-27 10:08 ` |SUCCESS| " dpdklab
2024-03-27 10:08 ` dpdklab
2024-03-27 10:09 ` dpdklab
2024-03-27 10:10 ` dpdklab
2024-03-27 10:10 ` |WARNING| " dpdklab
2024-03-27 10:10 ` dpdklab
2024-03-27 10:11 ` |SUCCESS| " dpdklab
2024-03-27 10:11 ` dpdklab
2024-03-27 10:12 ` dpdklab
2024-03-27 10:12 ` |WARNING| " dpdklab
2024-03-27 10:12 ` |SUCCESS| " dpdklab
2024-03-27 10:13 ` dpdklab
2024-03-27 10:13 ` |WARNING| " dpdklab
2024-03-27 10:13 ` |SUCCESS| " dpdklab
2024-03-27 10:14 ` dpdklab
2024-03-27 10:14 ` dpdklab
2024-03-27 10:15 ` dpdklab
2024-03-27 10:15 ` dpdklab
2024-03-27 10:16 ` |WARNING| " dpdklab
2024-03-27 10:16 ` |SUCCESS| " dpdklab
2024-03-27 10:16 ` dpdklab
2024-03-27 10:17 ` dpdklab
2024-03-27 10:18 ` dpdklab
2024-03-27 10:20 ` dpdklab
2024-03-27 10:21 ` dpdklab
2024-03-27 10:21 ` dpdklab
2024-03-27 10:22 ` dpdklab
2024-03-27 10:24 ` dpdklab
2024-03-27 10:24 ` dpdklab
2024-03-27 10:27 ` dpdklab
2024-03-27 10:28 ` dpdklab
2024-03-27 10:29 ` dpdklab
2024-03-27 10:29 ` dpdklab
2024-03-27 10:29 ` dpdklab
2024-03-27 10:31 ` dpdklab
2024-03-27 10:33 ` dpdklab
2024-03-27 10:54 ` dpdklab
2024-03-27 11:09 ` dpdklab
2024-03-27 11:34 ` dpdklab
2024-03-27 11:35 ` dpdklab
2024-03-27 12:53 ` dpdklab
2024-03-27 13:25 ` dpdklab
2024-04-02  7:32 ` dpdklab
2024-04-02  7:36 ` dpdklab
2024-04-02  7:56 ` dpdklab
2024-04-02  8:00 ` dpdklab
2024-04-02  8:04 ` 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=20240327100508.1285301-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=rjarry@redhat.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).