automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: marcinx.danilewicz@intel.com, robot@bytheb.org
Subject: |FAILURE| pw111031 [PATCH] sched: enable CMAN at runtime
Date: Wed, 11 May 2022 11:20:05 -0400	[thread overview]
Message-ID: <20220511152005.31162-1-robot@bytheb.org> (raw)
In-Reply-To: <20220511135304.258809-1-marcinx.danilewicz@intel.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/2307534891
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-shared-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
          type size hasn't changed
          1 data member change:
            type of 'rte_sched_cman_params* rte_sched_subport_params::cman_params' changed:
              in pointed to type 'struct rte_sched_cman_params' at rte_sched.h:166:1:
                type size hasn't changed
                1 data member change:
                  type of 'rte_sched_cman_mode rte_sched_cman_params::cman_mode' changed:
                    type size hasn't changed
                    1 enumerator insertion:
                      'rte_sched_cman_mode::RTE_SCHED_CMAN_NONE' value '0'
                    2 enumerator changes:
                      'rte_sched_cman_mode::RTE_SCHED_CMAN_RED' from value '0' to '1' at rte_sched.h:128:1
                      'rte_sched_cman_mode::RTE_SCHED_CMAN_PIE' from value '1' to '2' at rte_sched.h:128:1

Error: ABI issue reported for 'abidiff --suppr devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 install/usr/local/include reference/dump/librte_sched.dump install/dump/librte_sched.dump'
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).


Functions changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added variables

Functions changes summary: 0 Removed, 0 Changed, 0 Added function
Variables changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added variable

##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2022-05-11 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220511135304.258809-1-marcinx.danilewicz@intel.com>
2022-05-11 13:53 ` |SUCCESS| " checkpatch
2022-05-11 15:20 ` 0-day Robot [this message]
2022-05-12  9:11 |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=20220511152005.31162-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=marcinx.danilewicz@intel.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).