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| pw86474-86483 [PATCH] [v2, 10/10] compress/mlx5: add the supported capabilities
Date: Wed, 13 Jan 2021 12:14:22 -0500 (EST)	[thread overview]
Message-ID: <20210113171422.2E84230625@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: Performance-Testing
Test-Status: FAILURE
http://dpdk.org/patch/86474

_build patch failure_

Submitter: Matan Azrad <matan@nvidia.com>
Date: Wednesday, January 13 2021 16:18:10 
Applied on: CommitID:9b27a37b847237bc7b4f8369e1dad2dce3cdbb44
Apply patch set 86474-86483 failed:

[1/552] Linking static target drivers/libtmp_rte_crypto_ccp.a.
[2/552] Linking static target drivers/libtmp_rte_crypto_dpaa_sec.a.
[3/552] Linking static target drivers/libtmp_rte_crypto_openssl.a.
[4/552] Linking static target drivers/libtmp_rte_net_mlx5.a.
[5/552] Linking static target drivers/libtmp_rte_crypto_octeontx2.a.
[6/552] Linking static target drivers/libtmp_rte_crypto_scheduler.a.
[7/552] Linking static target drivers/libtmp_rte_compress_octeontx.a.
[8/552] Linking static target drivers/libtmp_rte_compress_zlib.a.
[9/552] Linking static target drivers/libtmp_rte_regex_mlx5.a.
[10/552] Compiling C object 'drivers/a715181@@rte_crypto_caam_jr@sta/meson-generated_.._rte_crypto_caam_jr.pmd.c.o'.
[11/552] Generating rte_crypto_dpaa_sec.pmd.c with a custom command.
[12/552] Compiling C object 'drivers/a715181@@rte_crypto_caam_jr@sha/meson-generated_.._rte_crypto_caam_jr.pmd.c.o'.
[13/552] Compiling C object 'drivers/a715181@@rte_crypto_virtio@sta/meson-generated_.._rte_crypto_virtio.pmd.c.o'.
[14/552] Compiling C object 'drivers/a715181@@rte_crypto_virtio@sha/meson-generated_.._rte_crypto_virtio.pmd.c.o'.
[15/552] Generating rte_crypto_openssl.pmd.c with a custom command.
[16/552] Generating rte_compress_octeontx.pmd.c with a custom command.
[17/552] Linking static target drivers/librte_crypto_caam_jr.a.
[18/552] Generating rte_crypto_ccp.pmd.c with a custom command.
[19/552] Generating rte_compress_zlib.pmd.c with a custom command.
[20/552] Linking static target drivers/librte_crypto_virtio.a.
[21/552] Generating rte_regex_mlx5_def with a custom command.
[22/552] Generating rte_regex_mlx5_mingw with a custom command.
[23/552] Linking target drivers/librte_crypto_null.so.21.1.
[24/552] Generating rte_regex_mlx5.pmd.c with a custom command.
[25/552] Compiling C object 'drivers/a715181@@rte_crypto_dpaa_sec@sta/meson-generated_.._rte_crypto_dpaa_sec.pmd.c.o'.
[26/552] Generating rte_crypto_octeontx2.pmd.c with a custom command.
[27/552] Generating rte_crypto_scheduler.pmd.c with a custom command.
[28/552] Compiling C object 'drivers/a715181@@rte_crypto_dpaa_sec@sha/meson-generated_.._rte_crypto_dpaa_sec.pmd.c.o'.
[29/552] Compiling C object 'drivers/a715181@@rte_crypto_openssl@sta/meson-generated_.._rte_crypto_openssl.pmd.c.o'.
[30/552] Compiling C object 'drivers/a715181@@rte_crypto_openssl@sha/meson-generated_.._rte_crypto_openssl.pmd.c.o'.
[31/552] Compiling C object 'drivers/a715181@@rte_crypto_ccp@sta/meson-generated_.._rte_crypto_ccp.pmd.c.o'.
[32/552] Compiling C object 'drivers/a715181@@rte_crypto_ccp@sha/meson-generated_.._rte_crypto_ccp.pmd.c.o'.
[33/552] Compiling C object 'drivers/a715181@@rte_compress_octeontx@sta/meson-generated_.._rte_compress_octeontx.pmd.c.o'.
[34/552] Compiling C object 'drivers/a715181@@rte_compress_octeontx@sha/meson-generated_.._rte_compress_octeontx.pmd.c.o'.
[35/552] Compiling C object 'drivers/a715181@@rte_compress_zlib@sta/meson-generated_.._rte_compress_zlib.pmd.c.o'.
[36/552] Compiling C object 'drivers/a715181@@rte_compress_zlib@sha/meson-generated_.._rte_compress_zlib.pmd.c.o'.
[37/552] Linking static target drivers/librte_crypto_openssl.a.
[38/552] Linking static target drivers/librte_crypto_ccp.a.
[39/552] Linking static target drivers/librte_compress_octeontx.a.
[40/552] Linking static target drivers/librte_crypto_dpaa_sec.a.
[41/552] Compiling C object 'drivers/a715181@@rte_crypto_octeontx2@sta/meson-generated_.._rte_crypto_octeontx2.pmd.c.o'.
[42/552] Compiling C object 'drivers/a715181@@rte_crypto_scheduler@sta/meson-generated_.._rte_crypto_scheduler.pmd.c.o'.
[43/552] Compiling C object 'drivers/a715181@@rte_crypto_scheduler@sha/meson-generated_.._rte_crypto_scheduler.pmd.c.o'.
[44/552] Compiling C object 'drivers/a715181@@rte_regex_mlx5@sta/meson-generated_.._rte_regex_mlx5.pmd.c.o'.
[45/552] Compiling C object 'drivers/a715181@@rte_crypto_octeontx2@sha/meson-generated_.._rte_crypto_octeontx2.pmd.c.o'.
[46/552] Compiling C object 'drivers/a715181@@rte_regex_mlx5@sha/meson-generated_.._rte_regex_mlx5.pmd.c.o'.
[47/552] Linking static target drivers/librte_compress_zlib.a.
[48/552] Linking static target drivers/librte_crypto_octeontx2.a.
[49/552] Linking static target drivers/librte_crypto_scheduler.a.
[50/552] Linking static target drivers/librte_regex_mlx5.a.
[51/552] Generating rte_regex_octeontx2_mingw with a custom command.
[52/552] Generating rte_regex_octeontx2_def with a custom command.
[53/552] Generating rte_net_mlx5.pmd.c with a custom command.
[54/552] Compiling C object 'drivers/a715181@@tmp_rte_compress_mlx5@sta/compress_mlx5_mlx5_compress.c.o'.
FAILED: drivers/a715181@@tmp_rte_compress_mlx5@sta/compress_mlx5_mlx5_compress.c.o 
cc -Idrivers/a715181@@tmp_rte_compress_mlx5@sta -Idrivers -I../drivers -Idrivers/compress/mlx5 -I../drivers/compress/mlx5 -Ilib/librte_compressdev -I../lib/librte_compressdev -I. -I../ -Iconfig -I../config -Ilib/librte_eal/include -I../lib/librte_eal/include -Ilib/librte_eal/linux/include -I../lib/librte_eal/linux/include -Ilib/librte_eal/x86/include -I../lib/librte_eal/x86/include -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_telemetry/../librte_metrics -I../lib/librte_telemetry/../librte_metrics -Ilib/librte_telemetry -I../lib/librte_telemetry -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Idrivers/common/mlx5 -I../drivers/common/mlx5 -Idrivers/common/mlx5/linux -I../drivers/common/mlx5/linux -Ilib/librte_hash -I../lib/librte_hash -Ilib/librte_rcu -I../lib/librte_rcu -Ilib/librte_pci -I../lib/librte_pci -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/librte_net -I../lib/librte_net -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 -std=c11 -Wno-strict-prototypes -D_BSD_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -MD -MQ 'drivers/a715181@@tmp_rte_compress_mlx5@sta/compress_mlx5_mlx5_compress.c.o' -MF 'drivers/a715181@@tmp_rte_compress_mlx5@sta/compress_mlx5_mlx5_compress.c.o.d' -o 'drivers/a715181@@tmp_rte_compress_mlx5@sta/compress_mlx5_mlx5_compress.c.o' -c ../drivers/compress/mlx5/mlx5_compress.c
../drivers/compress/mlx5/mlx5_compress.c:19:10: fatal error: mlx5_common_devx.h: No such file or directory
 #include <mlx5_common_devx.h>
          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
[55/552] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_ifc@sta/vdpa_ifc_base_ifcvf.c.o'.
[56/552] Compiling C object 'drivers/a715181@@rte_net_mlx5@sta/meson-generated_.._rte_net_mlx5.pmd.c.o'.
[57/552] Compiling C object 'drivers/a715181@@tmp_rte_regex_octeontx2@sta/regex_octeontx2_otx2_regexdev_hw_access.c.o'.
[58/552] Compiling C object 'drivers/a715181@@tmp_rte_regex_octeontx2@sta/regex_octeontx2_otx2_regexdev_compiler.c.o'.
[59/552] Compiling C object 'drivers/a715181@@tmp_rte_regex_octeontx2@sta/regex_octeontx2_otx2_regexdev_mbox.c.o'.
[60/552] Generating rte_crypto_caam_jr.sym_chk with a meson_exe.py custom command.
[61/552] Generating rte_crypto_virtio.sym_chk with a meson_exe.py custom command.
[62/552] Generating rte_crypto_openssl.sym_chk with a meson_exe.py custom command.
[63/552] Generating rte_compress_octeontx.sym_chk with a meson_exe.py custom command.
[64/552] Generating rte_crypto_dpaa_sec.sym_chk with a meson_exe.py custom command.
[65/552] Generating rte_crypto_ccp.sym_chk with a meson_exe.py custom command.
[66/552] Generating rte_compress_zlib.sym_chk with a meson_exe.py custom command.
[67/552] Generating rte_crypto_octeontx2.sym_chk with a meson_exe.py custom command.
[68/552] Generating rte_crypto_scheduler.sym_chk with a meson_exe.py custom command.
[69/552] Generating rte_regex_mlx5.sym_chk with a meson_exe.py custom command.
[70/552] Compiling C object 'drivers/a715181@@tmp_rte_regex_octeontx2@sta/regex_octeontx2_otx2_regexdev.c.o'.
[71/552] Compiling C object 'drivers/a715181@@tmp_rte_vdpa_ifc@sta/vdpa_ifc_ifcvf_vdpa.c.o'.
ninja: build stopped: subcommand failed.

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

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-01-13 17:14 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=20210113171422.2E84230625@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).