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
Subject: |WARNING| pw148425-148429 [PATCH] [RFC,5/5] test: remove unneeded me
Date: Sat, 16 Nov 2024 13:44:52 -0800 (PST)	[thread overview]
Message-ID: <67391254.250a0220.2e4b4f.6a77SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241113185720.28706-6-stephen@networkplumber.org>

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, November 13 2024 18:56:04 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c5df7a373ad07413d9652479272cd16adf989b06

148425-148429 --> testing issues

Upstream job id: ACVP-FIPS-testing#7989

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
[949/3099] Linking static target drivers/libtmp_rte_mempool_dpaa2.a
[950/3099] Generating rte_mempool_dpaa.pmd.c with a custom command
[951/3099] Compiling C object drivers/libtmp_rte_mempool_stack.a.p/mempool_stack_rte_mempool_stack.c.o
[952/3099] Generating rte_mempool_cnxk.pmd.c with a custom command
[953/3099] Generating rte_mempool_octeontx.pmd.c with a custom command
[954/3099] Compiling C object drivers/libtmp_rte_mempool_ring.a.p/mempool_ring_rte_mempool_ring.c.o
[955/3099] Compiling C object drivers/libtmp_rte_dma_hisilicon.a.p/dma_hisilicon_hisi_dmadev.c.o
[956/3099] Compiling C object drivers/libtmp_rte_dma_cnxk.a.p/dma_cnxk_cnxk_dmadev.c.o
[957/3099] Compiling C object drivers/libtmp_rte_dma_idxd.a.p/dma_idxd_idxd_common.c.o
[958/3099] Compiling C object drivers/libtmp_rte_mempool_bucket.a.p/mempool_bucket_rte_mempool_bucket.c.o
[959/3099] Compiling C object drivers/libtmp_rte_dma_dpaa2.a.p/dma_dpaa2_dpaa2_qdma.c.o
[960/3099] Compiling C object drivers/libtmp_rte_dma_cnxk.a.p/dma_cnxk_cnxk_dmadev_fp.c.o
[961/3099] Compiling C object drivers/libtmp_rte_dma_dpaa.a.p/dma_dpaa_dpaa_qdma.c.o
[962/3099] Generating rte_common_mlx5.sym_chk with a custom command (wrapped by meson to capture output)
[963/3099] Generating pipeline.sym_chk with a custom command (wrapped by meson to capture output)
[964/3099] Generating rte_common_sfc_efx.sym_chk with a custom command (wrapped by meson to capture output)
[965/3099] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-11-16 21:44 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241113185720.28706-6-stephen@networkplumber.org>
2024-11-13 18:28 ` |FAILURE| pw148425-148429 [RFC 5/5] test: remove unneeded memset qemudev
2024-11-13 18:59 ` |SUCCESS| pw148429 " checkpatch
2024-11-13 19:45 ` |FAILURE| " 0-day Robot
2024-11-13 21:00 ` |SUCCESS| pw148425-148429 [PATCH] [RFC,5/5] test: remove unneeded me dpdklab
2024-11-13 21:57 ` dpdklab
2024-11-13 22:58 ` dpdklab
2024-11-13 23:28 ` dpdklab
2024-11-13 23:59 ` |FAILURE| " dpdklab
2024-11-14  0:12 ` |WARNING| " dpdklab
2024-11-14  0:12 ` dpdklab
2024-11-14  0:31 ` |PENDING| " dpdklab
2024-11-14  0:49 ` |FAILURE| " dpdklab
2024-11-14  0:50 ` dpdklab
2024-11-14  0:52 ` dpdklab
2024-11-14  0:53 ` dpdklab
2024-11-14  0:54 ` |PENDING| " dpdklab
2024-11-14  0:54 ` |FAILURE| " dpdklab
2024-11-14  0:56 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  1:00 ` dpdklab
2024-11-14  1:00 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:02 ` dpdklab
2024-11-14  1:02 ` |WARNING| " dpdklab
2024-11-14  1:03 ` dpdklab
2024-11-14  1:18 ` dpdklab
2024-11-14  1:18 ` dpdklab
2024-11-14  1:39 ` dpdklab
2024-11-14  2:02 ` |FAILURE| " dpdklab
2024-11-14  2:03 ` dpdklab
2024-11-14  2:04 ` dpdklab
2024-11-14  2:06 ` dpdklab
2024-11-14  2:21 ` |PENDING| " dpdklab
2024-11-14  2:22 ` |WARNING| " dpdklab
2024-11-14  2:23 ` dpdklab
2024-11-14  2:59 ` |FAILURE| " dpdklab
2024-11-14  3:07 ` dpdklab
2024-11-14  3:23 ` dpdklab
2024-11-14  3:23 ` dpdklab
2024-11-14  3:44 ` |WARNING| " dpdklab
2024-11-14  3:45 ` dpdklab
2024-11-14  4:24 ` |FAILURE| " dpdklab
2024-11-14  4:28 ` dpdklab
2024-11-16 16:23 ` dpdklab
2024-11-16 16:46 ` dpdklab
2024-11-16 21:05 ` |WARNING| " dpdklab
2024-11-16 21:06 ` |FAILURE| " dpdklab
2024-11-16 21:12 ` dpdklab
2024-11-16 21:36 ` |WARNING| " dpdklab
2024-11-16 21:44 ` dpdklab [this message]
2024-11-16 21:55 ` |FAILURE| " dpdklab
2024-11-16 22:01 ` dpdklab
2024-11-16 22:07 ` |WARNING| " 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=67391254.250a0220.2e4b4f.6a77SMTPIN_ADDED_MISSING@mx.google.com \
    --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).