automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |FAILURE| pw93373 [PATCH] [v2, 3/3] net/sfc: support matching on VLAN presence in transfer rules
Date: Sun, 23 May 2021 08:46:26 -0400 (EDT)	[thread overview]
Message-ID: <20210523124626.378578904B@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 10967 bytes --]

Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/93373

_build patch failure_

Submitter: Ivan Malov <Ivan.Malov@oktetlabs.ru>
Date: Saturday, May 22 2021 19:32:56 
Applied on: CommitID:175af25734f295874e31b33ccd0879e69fd152a9
Apply patch set 93373 failed:

[1/948] Linking static target drivers/libtmp_rte_net_qede.a
[2/948] Linking static target drivers/libtmp_rte_net_mlx5.a
[3/948] Linking static target drivers/libtmp_rte_net_octeontx2.a
[4/948] Compiling C object drivers/librte_net_ring.a.p/meson-generated_.._rte_net_ring.pmd.c.o
[5/948] Compiling C object drivers/librte_net_ring.so.21.2.p/meson-generated_.._rte_net_ring.pmd.c.o
[6/948] Linking static target drivers/librte_net_ring.a
[7/948] Generating rte_net_qede.pmd.c with a custom command
[8/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_swq.c.o
[9/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_link.c.o
[10/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_cryptodev.c.o
[11/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_mempool.c.o
[12/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_tap.c.o
[13/948] Compiling C object drivers/librte_net_qede.so.21.2.p/meson-generated_.._rte_net_qede.pmd.c.o
[14/948] Compiling C object drivers/librte_net_qede.a.p/meson-generated_.._rte_net_qede.pmd.c.o
[15/948] Generating rte_net_softnic_def with a custom command
[16/948] Compiling C object drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_mae.c.o
FAILED: drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_mae.c.o 
cc -Idrivers/libtmp_rte_net_sfc.a.p -Idrivers -I../drivers -Idrivers/net/sfc -I../drivers/net/sfc -Ilib/ethdev -I../lib/ethdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Idrivers/common/sfc_efx -I../drivers/common/sfc_efx -Idrivers/common/sfc_efx/base -I../drivers/common/sfc_efx/base -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O3 -include rte_config.h -Wextra -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-missing-field-initializers -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-strict-aliasing -Wdisabled-optimization -Waggregate-return -Wbad-function-cast -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.sfc -MD -MQ drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_mae.c.o -MF drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_mae.c.o.d -o drivers/libtmp_rte_net_sfc.a.p/net_sfc_sfc_mae.c.o -c ../drivers/net/sfc/sfc_mae.c
../drivers/net/sfc/sfc_mae.c: In function ‘sfc_mae_rule_process_pattern_data’:
../drivers/net/sfc/sfc_mae.c:833:8: warning: implicit declaration of function ‘efx_mae_match_spec_bit_set’; did you mean ‘efx_mae_match_spec_mport_set’? [-Wimplicit-function-declaration]
   rc = efx_mae_match_spec_bit_set(ctx->match_spec,
        ^~~~~~~~~~~~~~~~~~~~~~~~~~
        efx_mae_match_spec_mport_set
../drivers/net/sfc/sfc_mae.c:833:8: warning: nested extern declaration of ‘efx_mae_match_spec_bit_set’ [-Wnested-externs]
../drivers/net/sfc/sfc_mae.c:834:14: error: ‘EFX_MAE_FIELD_HAS_OVLAN’ undeclared (first use in this function); did you mean ‘EFX_MAE_FIELD_IP_TTL’?
       fremap[EFX_MAE_FIELD_HAS_OVLAN],
              ^~~~~~~~~~~~~~~~~~~~~~~
              EFX_MAE_FIELD_IP_TTL
../drivers/net/sfc/sfc_mae.c:834:14: note: each undeclared identifier is reported only once for each function it appears in
../drivers/net/sfc/sfc_mae.c:843:14: error: ‘EFX_MAE_FIELD_HAS_IVLAN’ undeclared (first use in this function); did you mean ‘EFX_MAE_FIELD_HAS_OVLAN’?
       fremap[EFX_MAE_FIELD_HAS_IVLAN],
              ^~~~~~~~~~~~~~~~~~~~~~~
              EFX_MAE_FIELD_HAS_OVLAN
../drivers/net/sfc/sfc_mae.c: At top level:
../drivers/net/sfc/sfc_mae.c:1682:3: error: ‘EFX_MAE_FIELD_HAS_OVLAN’ undeclared here (not in a function); did you mean ‘EFX_MAE_FIELD_IP_TTL’?
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1701:2: note: in expansion of macro ‘FIELD_ID_NO_REMAP’
  FIELD_ID_NO_REMAP(HAS_OVLAN),
  ^~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1682:3: error: array index in initializer not of integer type
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1701:2: note: in expansion of macro ‘FIELD_ID_NO_REMAP’
  FIELD_ID_NO_REMAP(HAS_OVLAN),
  ^~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1682:3: note: (near initialization for ‘field_ids_no_remap’)
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1701:2: note: in expansion of macro ‘FIELD_ID_NO_REMAP’
  FIELD_ID_NO_REMAP(HAS_OVLAN),
  ^~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1682:3: error: ‘EFX_MAE_FIELD_HAS_IVLAN’ undeclared here (not in a function); did you mean ‘EFX_MAE_FIELD_HAS_OVLAN’?
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1702:2: note: in expansion of macro ‘FIELD_ID_NO_REMAP’
  FIELD_ID_NO_REMAP(HAS_IVLAN),
  ^~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1682:3: error: array index in initializer not of integer type
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1702:2: note: in expansion of macro ‘FIELD_ID_NO_REMAP’
  FIELD_ID_NO_REMAP(HAS_IVLAN),
  ^~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1682:3: note: (near initialization for ‘field_ids_no_remap’)
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1702:2: note: in expansion of macro ‘FIELD_ID_NO_REMAP’
  FIELD_ID_NO_REMAP(HAS_IVLAN),
  ^~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1715:3: error: array index in initializer not of integer type
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_ENC_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1733:2: note: in expansion of macro ‘FIELD_ID_REMAP_TO_ENCAP’
  FIELD_ID_REMAP_TO_ENCAP(HAS_OVLAN),
  ^~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1715:3: note: (near initialization for ‘field_ids_remap_to_encap’)
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_ENC_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1733:2: note: in expansion of macro ‘FIELD_ID_REMAP_TO_ENCAP’
  FIELD_ID_REMAP_TO_ENCAP(HAS_OVLAN),
  ^~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1715:29: error: ‘EFX_MAE_FIELD_ENC_HAS_OVLAN’ undeclared here (not in a function); did you mean ‘EFX_MAE_FIELD_HAS_OVLAN’?
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_ENC_##_field
                             ^
../drivers/net/sfc/sfc_mae.c:1733:2: note: in expansion of macro ‘FIELD_ID_REMAP_TO_ENCAP’
  FIELD_ID_REMAP_TO_ENCAP(HAS_OVLAN),
  ^~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1715:29: error: incompatible types when initializing type ‘enum efx_mae_field_id_e’ using type ‘const efx_mae_field_id_t * {aka const enum efx_mae_field_id_e *}’
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_ENC_##_field
                             ^
../drivers/net/sfc/sfc_mae.c:1733:2: note: in expansion of macro ‘FIELD_ID_REMAP_TO_ENCAP’
  FIELD_ID_REMAP_TO_ENCAP(HAS_OVLAN),
  ^~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1715:3: error: array index in initializer not of integer type
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_ENC_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1734:2: note: in expansion of macro ‘FIELD_ID_REMAP_TO_ENCAP’
  FIELD_ID_REMAP_TO_ENCAP(HAS_IVLAN),
  ^~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1715:3: note: (near initialization for ‘field_ids_remap_to_encap’)
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_ENC_##_field
   ^
../drivers/net/sfc/sfc_mae.c:1734:2: note: in expansion of macro ‘FIELD_ID_REMAP_TO_ENCAP’
  FIELD_ID_REMAP_TO_ENCAP(HAS_IVLAN),
  ^~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1715:29: error: ‘EFX_MAE_FIELD_ENC_HAS_IVLAN’ undeclared here (not in a function); did you mean ‘EFX_MAE_FIELD_ENC_HAS_OVLAN’?
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_ENC_##_field
                             ^
../drivers/net/sfc/sfc_mae.c:1734:2: note: in expansion of macro ‘FIELD_ID_REMAP_TO_ENCAP’
  FIELD_ID_REMAP_TO_ENCAP(HAS_IVLAN),
  ^~~~~~~~~~~~~~~~~~~~~~~
../drivers/net/sfc/sfc_mae.c:1715:29: error: incompatible types when initializing type ‘enum efx_mae_field_id_e’ using type ‘const efx_mae_field_id_t * {aka const enum efx_mae_field_id_e *}’
  [EFX_MAE_FIELD_##_field] = EFX_MAE_FIELD_ENC_##_field
                             ^
../drivers/net/sfc/sfc_mae.c:1734:2: note: in expansion of macro ‘FIELD_ID_REMAP_TO_ENCAP’
  FIELD_ID_REMAP_TO_ENCAP(HAS_IVLAN),
  ^~~~~~~~~~~~~~~~~~~~~~~
[17/948] Linking static target drivers/librte_net_qede.a
[18/948] Generating rte_net_softnic_mingw with a custom command
[19/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_parser.c.o
[20/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_action.c.o
[21/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_meter.c.o
[22/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_pipeline.c.o
[23/948] Generating rte_net_octeontx2.pmd.c with a custom command
[24/948] Generating rte_net_mlx5.pmd.c with a custom command
[25/948] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_tap_bpf_api.c.o
[26/948] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_tap_intr.c.o
[27/948] Generating rte_net_ring.sym_chk with a custom command (wrapped by meson to capture output)
[28/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_flow.c.o
[29/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_tm.c.o
[30/948] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_tap_flow.c.o
[31/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_thread.c.o
[32/948] Compiling C object drivers/libtmp_rte_net_softnic.a.p/net_softnic_rte_eth_softnic_cli.c.o
[33/948] Compiling C object drivers/libtmp_rte_net_tap.a.p/net_tap_rte_eth_tap.c.o
ninja: build stopped: subcommand failed.

https://lab.dpdk.org/results/dashboard/patchsets/17174/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-05-23 12:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210523124626.378578904B@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).