automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: kumaraparamesh92@gmail.com, robot@bytheb.org
Subject: |FAILURE| pw149564 [PATCH] lib/gro: use hash function for flow lookup
Date: Wed,  1 Jan 2025 05:24:33 -0500	[thread overview]
Message-ID: <20250101102433.866574-1-robot@bytheb.org> (raw)
In-Reply-To: <20250101093735.95271-1-kumaraparamesh92@gmail.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/12569431451
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-static-mingw" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-static-mingw" at step Build and test
####################################################################################
  232 |   tcp_tbl.flow_num = 0;
      |          ^
../lib/gro/rte_gro.c:233:10: error: ‘struct gro_tcp4_tbl’ has no member named ‘item_num’
  233 |   tcp_tbl.item_num = 0;
      |          ^
../lib/gro/rte_gro.c:234:10: error: ‘struct gro_tcp4_tbl’ has no member named ‘max_flow_num’
  234 |   tcp_tbl.max_flow_num = item_num;
      |          ^
../lib/gro/rte_gro.c:235:10: error: ‘struct gro_tcp4_tbl’ has no member named ‘max_item_num’
  235 |   tcp_tbl.max_item_num = item_num;
      |          ^
[217/2972] Compiling C object lib/librte_gro.a.p/gro_gro_udp4.c.obj
[218/2972] Compiling C object lib/librte_gro.a.p/gro_gro_vxlan_tcp4.c.obj
FAILED: lib/librte_gro.a.p/gro_gro_vxlan_tcp4.c.obj 
ccache x86_64-w64-mingw32-gcc -Ilib/librte_gro.a.p -Ilib -I../lib -Ilib/gro -I../lib/gro -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/windows/include -I../lib/eal/windows/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/log -I../lib/log -Ilib/kvargs -I../lib/kvargs -Ilib/ethdev -I../lib/ethdev -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/meter -I../lib/meter -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O2 -g -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -D_WIN32_WINNT=0x0A00 -D__USE_MINGW_ANSI_STDIO -march=native -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DRTE_LOG_DEFAULT_LOGTYPE=lib.gro -MD -MQ lib/librte_gro.a.p/gro_gro_vxlan_tcp4.c.obj -MF lib/librte_gro.a.p/gro_gro_vxlan_tcp4.c.obj.d -o lib/librte_gro.a.p/gro_gro_vxlan_tcp4.c.obj -c ../lib/gro/gro_vxlan_tcp4.c
In file included from ../lib/gro/gro_vxlan_tcp4.h:8,
                 from ../lib/gro/gro_vxlan_tcp4.c:10:
../lib/gro/gro_tcp4.h:27:2: error: expected specifier-qualifier-list before ‘STAILQ_ENTRY’
   27 |  STAILQ_ENTRY(gro_tcp4_flow) next;
      |  ^~~~~~~~~~~~
../lib/gro/gro_tcp4.h:39:2: error: expected specifier-qualifier-list before ‘STAILQ_HEAD’
   39 |  STAILQ_HEAD(, gro_tcp4_flow) collision_list[GRO_TCP4_HASH_BUCKET_SIZE];
      |  ^~~~~~~~~~~
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-static-mingw" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2025-01-01 10:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250101093735.95271-1-kumaraparamesh92@gmail.com>
2025-01-01  9:07 ` |SUCCESS| " qemudev
2025-01-01  9:11 ` qemudev
2025-01-01  9:37 ` checkpatch
2025-01-01 10:24 ` 0-day Robot [this message]
2025-01-02 21:45 ` |SUCCESS| pw149564 [PATCH] lib/gro: use hash function for flow looku dpdklab
2025-01-02 22:18 ` dpdklab
2025-01-02 22:20 ` dpdklab
2025-01-02 22:42 ` dpdklab
2025-01-02 23:17 ` dpdklab
2025-01-02 23:38 ` dpdklab
2025-01-02 23:49 ` dpdklab
2025-01-03  0:03 ` |PENDING| " dpdklab
2025-01-03  0:29 ` |SUCCESS| " dpdklab
2025-01-03  2:13 ` |FAILURE| " dpdklab
2025-01-03  3:07 ` |WARNING| " dpdklab
2025-01-03  5:50 ` |SUCCESS| " dpdklab
2025-01-06 19:37 ` |PENDING| " dpdklab
2025-01-06 20:37 ` |SUCCESS| " 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=20250101102433.866574-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=kumaraparamesh92@gmail.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).