automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: ndabilpuram@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw152753 [RFC PATCH 4/4] net/cnxk: report link type along with link status
Date: Thu,  3 Apr 2025 04:02:25 -0400	[thread overview]
Message-ID: <20250403080225.4035693-1-robot@bytheb.org> (raw)
In-Reply-To: <20250403070837.926292-4-ndabilpuram@marvell.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/14237301574
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-abi+debug+doc+examples+tests" failed at step Build and test
"ubuntu-22.04-clang-asan+doc+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, 1 Changed (17 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added variables

1 function with some indirect sub-type change:

  [C] 'function int rte_eth_link_get(uint16_t, rte_eth_link*)' at rte_ethdev.c:3082:1 has some indirect sub-type changes:
    parameter 2 of type 'rte_eth_link*' has sub-type changes:
      in pointed to type 'struct rte_eth_link' at rte_ethdev.h:348:1:
        type size hasn't changed
        1 data member change:
          anonymous data member at offset 0 (in bits) changed from:
            union {uint64_t val64; struct {uint32_t link_speed; uint16_t link_duplex; uint16_t link_autoneg; uint16_t link_status;};}
          to:
            union {uint64_t val64; struct {uint32_t link_speed; uint16_t link_duplex; uint16_t link_autoneg; uint16_t link_status; uint16_t link_type;};}

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/librte_ethdev.so.25.1 install/usr/local/lib/librte_ethdev.so.25.2
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
Functions changes summary: 0 Removed, 0 Changed (282 filtered out), 0 Added (1 filtered out) 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

##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
102/104 DPDK:fast-tests / vdev_autotest                 OK              0.34s
103/104 DPDK:fast-tests / version_autotest              OK              0.35s
104/104 DPDK:fast-tests / telemetry_all                 OK              1.10s


Ok:                 97  
Expected Fail:      0   
Fail:               1   
Unexpected Pass:    0   
Skipped:            6   
Timeout:            0   

Full log written to /home/runner/work/dpdk/dpdk/build/meson-logs/testlog.txt
+ failed=true
+ catch_coredump
+ ls /tmp/dpdk-core.*.*
+ return 0
+ check_traces
+ which babeltrace
+ sudo find /home/runner -name metadata
+ dirname /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-03-AM-08-00-42/metadata
+ sudo babeltrace /home/runner/work/dpdk/dpdk/build/app/test/suites/rte-2025-04-03-AM-08-00-42
+ continue
+ [ true != true ]
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-04-03  8:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250403070837.926292-4-ndabilpuram@marvell.com>
2025-04-03  6:35 ` |SUCCESS| pw152750-152753 " qemudev
2025-04-03  6:41 ` |FAILURE| " qemudev
2025-04-03  7:09 ` |SUCCESS| pw152753 " checkpatch
2025-04-03  8:02 ` 0-day Robot [this message]
2025-04-03  8:33 ` |SUCCESS| pw152750-152753 [PATCH] [RFC,4/4] net/cnxk: report link ty dpdklab
2025-04-03  8:39 ` dpdklab
2025-04-03  8:41 ` dpdklab
2025-04-03  8:55 ` dpdklab
2025-04-03  9:01 ` dpdklab
2025-04-03  9:03 ` dpdklab
2025-04-03  9:26 ` dpdklab
2025-04-03  9:37 ` |PENDING| " dpdklab
2025-04-03  9:48 ` |FAILURE| " dpdklab
2025-04-03  9:52 ` dpdklab
2025-04-03  9:53 ` dpdklab
2025-04-03  9:53 ` dpdklab
2025-04-03  9:58 ` dpdklab
2025-04-03 10:18 ` |PENDING| " dpdklab
2025-04-03 10:41 ` |FAILURE| " dpdklab
2025-04-03 10:50 ` |WARNING| " dpdklab
2025-04-03 11:41 ` |FAILURE| " dpdklab
2025-04-03 11:53 ` |SUCCESS| " dpdklab
2025-04-03 12:12 ` |FAILURE| " dpdklab
2025-04-03 12:59 ` dpdklab
2025-04-03 13:29 ` |SUCCESS| " dpdklab
2025-04-03 15:53 ` dpdklab
2025-04-03 19:32 ` dpdklab
2025-04-04  0:15 ` dpdklab
2025-04-04  0:41 ` dpdklab
2025-04-04 16:43 ` 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=20250403080225.4035693-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=ndabilpuram@marvell.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).