automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Xueming Li <xuemingl@nvidia.com>
Subject: |WARNING| pw125228 [PATCH] bus/auxiliary: support cleanup callback
Date: Mon, 20 Mar 2023 11:33:19 +0000 (UTC)	[thread overview]
Message-ID: <20230320113319.4775B60214@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/125228

_Testing issues_

Submitter: Xueming Li <xuemingl@nvidia.com>
Date: Friday, March 17 2023 14:55:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:bb1f2f5b181b9d8ea7fb28ca2024914fc57bd823

125228 --> testing fail

Test environment and result as below:

+--------------+----------------------+
| Environment  | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | WARN                 |
+--------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
|                                ^~~
cc1: all warnings being treated as errors
[444/3227] Compiling C object 'drivers/a715181@@rte_common_octeontx@sha/meson-generated_.._rte_common_octeontx.pmd.c.o'.
[445/3227] Linking static target drivers/librte_common_octeontx.a.
[446/3227] Generating table.sym_chk with a meson_exe.py custom command.
[447/3227] Generating rte_common_cpt.sym_chk with a meson_exe.py custom command.
[448/3227] Generating rte_common_iavf.sym_chk with a meson_exe.py custom command.
[449/3227] Compiling C object 'drivers/common/idpf/281975e@@idpf_common_avx512_lib@sta/idpf_common_rxtx_avx512.c.o'.
[450/3227] Compiling C object 'drivers/a715181@@tmp_rte_bus_auxiliary@sta/bus_auxiliary_linux_auxiliary.c.o'.
[451/3227] Compiling C object 'drivers/a715181@@tmp_rte_common_idpf@sta/common_idpf_idpf_common_rxtx.c.o'.
[452/3227] Generating rte_common_dpaax.sym_chk with a meson_exe.py custom command.
[453/3227] Generating graph.sym_chk with a meson_exe.py custom command.
[454/3227] Compiling C object 'drivers/a715181@@tmp_rte_bus_dpaa@sta/bus_dpaa_base_qbman_dpaa_alloc.c.o'.
[455/3227] Compiling C object 'drivers/a715181@@tmp_rte_bus_dpaa@sta/bus_dpaa_base_fman_fman.c.o'.
[456/3227] Generating ethdev.sym_chk with a meson_exe.py custom command.
[457/3227] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_swx_pipeline.c.o'.
[458/3227] Generating eal.sym_chk with a meson_exe.py custom command.
[459/3227] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_virtio_net.c.o'.
[460/3227] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_table_action.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25781/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

                 reply	other threads:[~2023-03-20 11:33 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=20230320113319.4775B60214@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xuemingl@nvidia.com \
    /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).