automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw135302-135318 [PATCH] [v4,17/17] log: mark PMD logtype a
Date: Mon, 18 Dec 2023 15:44:16 -0800 (PST)	[thread overview]
Message-ID: <6580d950.020a0220.b885e.be2fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/135318

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, December 18 2023 19:22:33 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135302-135318 --> 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
[473/2814] Linking target lib/librte_sched.so.24.1.
[474/2814] Linking target lib/librte_reorder.so.24.1.
[475/2814] Linking target lib/librte_mldev.so.24.1.
[476/2814] Linking static target drivers/libtmp_rte_common_cpt.a.
[477/2814] Linking static target lib/librte_node.a.
[478/2814] Linking target lib/librte_fib.so.24.1.
[479/2814] Generating symbol file 'lib/76b5a35@@rte_net@sha/librte_net.so.24.1.symbols'.
[480/2814] Generating symbol file 'lib/76b5a35@@rte_compressdev@sha/librte_compressdev.so.24.1.symbols'.
[481/2814] Generating symbol file 'lib/76b5a35@@rte_bbdev@sha/librte_bbdev.so.24.1.symbols'.
[482/2814] Generating symbol file 'lib/76b5a35@@rte_cryptodev@sha/librte_cryptodev.so.24.1.symbols'.
[483/2814] Generating symbol file 'lib/76b5a35@@rte_regexdev@sha/librte_regexdev.so.24.1.symbols'.
[484/2814] Generating graph.sym_chk with a meson_exe.py custom command.
[485/2814] Compiling C object 'drivers/a715181@@tmp_rte_common_iavf@sta/common_iavf_iavf_adminq.c.o'.
[486/2814] Compiling C object 'drivers/a715181@@tmp_rte_common_iavf@sta/common_iavf_iavf_common.c.o'.
[487/2814] Compiling C object 'lib/76b5a35@@rte_pipeline@sta/pipeline_rte_swx_pipeline.c.o'.
[488/2814] Compiling C object 'lib/76b5a35@@rte_vhost@sta/vhost_virtio_net.c.o'.
[489/2814] 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: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-18 23:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 23:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18 21:37 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=6580d950.020a0220.b885e.be2fSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).