automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: longli@linuxonhyperv.com, robot@bytheb.org
Subject: |FAILURE| pw152779 [Patch v3 6/6] bus/vmbus: set event for channel without monitoring support
Date: Fri,  4 Apr 2025 21:42:41 -0400	[thread overview]
Message-ID: <20250405014241.3358348-1-robot@bytheb.org> (raw)
In-Reply-To: <1743813338-28238-7-git-send-email-longli@linuxonhyperv.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/14276639607
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
####################################################################################
      type size changed from 32 to 0 (in bits)
    parameter 6 of type 'typedef uint64_t' changed:
      typedef name changed from uint64_t to uint32_t at stdint-uintn.h:26:1
      underlying type 'typedef __uint64_t' changed at types.h:45:1, as reported earlier
    parameter 7 of type 'bool*' changed:
      entity changed from 'bool*' to 'typedef uint64_t' at stdint-uintn.h:27:1
      type size hasn't changed
    parameter 8 of type 'bool*' was added

  [C] 'function void rte_vmbus_chan_signal_read(vmbus_channel*, uint32_t)' at vmbus_channel.c:191:1 has some indirect sub-type changes:
    parameter 2 of type 'typedef uint32_t' changed:
      entity changed from 'typedef uint32_t' to 'vmbus_channel*'
      type size changed from 32 to 64 (in bits)
    parameter 3 of type 'typedef uint32_t' was added

  [C] 'function void rte_vmbus_chan_signal_tx(const vmbus_channel*)' at vmbus_channel.c:80:1 has some indirect sub-type changes:
    parameter 1 of type 'const vmbus_channel*' changed:
      in pointed to type 'const vmbus_channel' at bus_vmbus_driver.h:33:1:
        entity changed from 'const vmbus_channel' to 'struct rte_vmbus_device' at bus_vmbus_driver.h:33:1
        type size changed from 640 to 2304 (in bits)
    parameter 2 of type 'const vmbus_channel*' was added

Error: ABI issue reported for abidiff --suppr /home/runner/work/dpdk/dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 install/usr/local/include reference/usr/local/lib/dpdk/pmds-25.1/librte_bus_vmbus.so.25.1 install/usr/local/lib/dpdk/pmds-25.2/librte_bus_vmbus.so.25.2
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
##[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:[~2025-04-05  1:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1743813338-28238-7-git-send-email-longli@linuxonhyperv.com>
2025-04-05  0:03 ` |SUCCESS| pw152774-152779 " qemudev
2025-04-05  0:07 ` qemudev
2025-04-05  0:37 ` |WARNING| pw152779 " checkpatch
2025-04-05  1:10 ` |SUCCESS| pw152774-152779 [PATCH] [v3,6/6] bus/vmbus: set event for dpdklab
2025-04-05  1:12 ` dpdklab
2025-04-05  1:15 ` dpdklab
2025-04-05  1:15 ` |PENDING| " dpdklab
2025-04-05  1:20 ` |WARNING| " dpdklab
2025-04-05  1:22 ` |SUCCESS| " dpdklab
2025-04-05  1:23 ` |PENDING| " dpdklab
2025-04-05  1:27 ` |SUCCESS| " dpdklab
2025-04-05  1:30 ` dpdklab
2025-04-05  1:31 ` |PENDING| " dpdklab
2025-04-05  1:32 ` |FAILURE| " dpdklab
2025-04-05  1:42 ` 0-day Robot [this message]
2025-04-05  1:43 ` dpdklab
2025-04-05  1:55 ` |SUCCESS| " dpdklab
2025-04-05  1:55 ` |FAILURE| " dpdklab
2025-04-05  1:58 ` |SUCCESS| " dpdklab
2025-04-05  2:03 ` |WARNING| " dpdklab
2025-04-05  2:21 ` |SUCCESS| " dpdklab
2025-04-05  3:00 ` 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=20250405014241.3358348-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=longli@linuxonhyperv.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).