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>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |WARNING| pw123419-123423 [PATCH] [5/5] ipsec: fix usage of RTE_LOGTYPE_USER1
Date: Sun, 12 Feb 2023 12:16:51 +0000 (UTC)	[thread overview]
Message-ID: <20230212121651.58F56601B6@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, February 08 2023 04:48:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a0c837ad1fb5b6a8b10a284ffeb5f9e31bd8ff00

123419-123423 --> 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
[249/3159] Compiling C object 'lib/76b5a35@@rte_ip_frag@sta/ip_frag_rte_ip_frag_common.c.o'.
[250/3159] Compiling C object 'lib/76b5a35@@rte_latencystats@sta/latencystats_rte_latencystats.c.o'.
[251/3159] Generating gso.sym_chk with a meson_exe.py custom command.
[252/3159] Compiling C object 'lib/76b5a35@@rte_lpm@sta/lpm_rte_lpm.c.o'.
[253/3159] Generating gpudev.sym_chk with a meson_exe.py custom command.
[254/3159] Compiling C object 'lib/76b5a35@@rte_lpm@sta/lpm_rte_lpm6.c.o'.
[255/3159] Compiling C object 'lib/76b5a35@@rte_member@sta/member_rte_member_vbf.c.o'.
[256/3159] Compiling C object 'drivers/a715181@@tmp_rte_common_cnxk@sta/common_cnxk_roc_nix_npc.c.o'.
[257/3159] Compiling C object 'drivers/a715181@@tmp_rte_common_cnxk@sta/common_cnxk_roc_nix_mcast.c.o'.
[258/3159] Compiling C object 'drivers/a715181@@tmp_rte_common_cnxk@sta/common_cnxk_roc_nix_inl_dev_irq.c.o'.
[259/3159] Compiling C object 'drivers/a715181@@tmp_rte_common_cnxk@sta/common_cnxk_roc_nix_inl_dev.c.o'.
[260/3159] Compiling C object 'drivers/a715181@@tmp_rte_common_cnxk@sta/common_cnxk_roc_nix_inl.c.o'.
[261/3159] Compiling C object 'lib/76b5a35@@rte_member@sta/member_rte_member_sketch.c.o'.
[262/3159] Generating eventdev.sym_chk with a meson_exe.py custom command.
[263/3159] Generating cryptodev.sym_chk with a meson_exe.py custom command.
[264/3159] Generating ethdev.sym_chk with a meson_exe.py custom command.
[265/3159] Generating eal.sym_chk with a meson_exe.py custom command.
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/25284/

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2023-02-12 12:25 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=20230212121651.58F56601B6@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=stephen@networkplumber.org \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).