automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: mb@smartsharesystems.com, robot@bytheb.org
Subject: |FAILURE| pw105919 [PATCH] mempool: optimize put objects to mempool with cache
Date: Mon, 17 Jan 2022 08:19:33 -0500	[thread overview]
Message-ID: <20220117131933.27178-1-robot@bytheb.org> (raw)
In-Reply-To: <20220117115231.8060-1-mb@smartsharesystems.com>

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-18.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).

  [C] 'function int rte_distributor_get_pkt(rte_distributor*, unsigned int, rte_mbuf**, rte_mbuf**, unsigned int)' at rte_distributor.c:131:1 has some indirect sub-type changes:
    parameter 4 of type 'rte_mbuf**' has sub-type changes:
      in pointed to type 'rte_mbuf*':
        in pointed to type 'struct rte_mbuf' at rte_mbuf_core.h:578:1:
          type size hasn't changed
          1 data member changes (1 filtered):
            type of 'rte_mempool* rte_mbuf::pool' changed:
              in pointed to type 'struct rte_mempool' at rte_mempool.h:213:1:
                type size hasn't changed
                1 data member changes (2 filtered):
                  type of 'rte_mempool_cache* rte_mempool::local_cache' changed:
                    in pointed to type 'struct rte_mempool_cache' at rte_mempool.h:89:1:
                      type size changed from 98816 to 66048 (in bits)
                      1 data member change:
                        type of 'void* rte_mempool_cache::objs[1536]' changed:
                          type name changed from 'void*[1536]' to 'void*[1024]'
                          array type size changed from 98304 to 65536
                          array type subrange 1 changed length from 1536 to 1024
                        and offset changed from 128 to 512 (in bits) (by +384 bits)



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

      parent reply	other threads:[~2022-01-17 12:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220117115231.8060-1-mb@smartsharesystems.com>
2022-01-17 11:52 ` |WARNING| " checkpatch
2022-01-17 13:19 ` 0-day Robot [this message]

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=20220117131933.27178-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=mb@smartsharesystems.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).