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| pw153337 [PATCH] [v2,1/1] buildtools: avoid break due to f
Date: Wed, 07 May 2025 10:48:10 -0700 (PDT)	[thread overview]
Message-ID: <681b9cda.050a0220.279a78.a068SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1746569662-11532-2-git-send-email-andremue@linux.microsoft.com>

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

_Testing issues_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Tuesday, May 06 2025 22:14:22 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:75f179ebe347b6098cf3af26d3d3b7168fe3fe24

153337 --> testing issues

Upstream job id: ACVP-FIPS-testing#9737

Test environment and result as below:

+--------------------+----------------------+----------------------+
|    Environment     | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04       | SKIPPED              | WARN                 |
+--------------------+----------------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
with Popen(*popenargs, **kwargs) as process:
File "/usr/lib/python3.8/subprocess.py", line 858, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'drivers/rte_common_ionic.pmd.c.p'
[612/3505] Compiling C object lib/librte_vhost.a.p/vhost_vhost_crypto.c.o
[613/3505] Generating symbol file lib/librte_graph.so.25.2.p/librte_graph.so.25.2.symbols
[614/3505] Compiling C object drivers/libtmp_rte_bus_cdx.a.p/bus_cdx_cdx.c.o
[615/3505] Compiling C object drivers/libtmp_rte_bus_cdx.a.p/bus_cdx_cdx_vfio.c.o
[616/3505] Generating node.sym_chk with a custom command (wrapped by meson to capture output)
[617/3505] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_fman_netcfg_layer.c.o
[618/3505] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_bman_driver.c.o
[619/3505] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_bman.c.o
[620/3505] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_fman_fman.c.o
[621/3505] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_fman_fman_hw.c.o
[622/3505] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_pipeline.c.o
[623/3505] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
[624/3505] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

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/33130/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-07 17:48 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1746569662-11532-2-git-send-email-andremue@linux.microsoft.com>
2025-05-06 21:40 ` |FAILURE| pw153337 [PATCH v2 1/1] buildtools: avoid break due to failure to cleanup temporary directory qemudev
2025-05-06 22:15 ` |SUCCESS| " checkpatch
2025-05-06 22:44 ` |FAILURE| " 0-day Robot
2025-05-07  1:32 ` |SUCCESS| pw153337 [PATCH] [v2,1/1] buildtools: avoid break due to f dpdklab
2025-05-07  1:32 ` dpdklab
2025-05-07  1:43 ` dpdklab
2025-05-07  1:43 ` dpdklab
2025-05-07  1:44 ` dpdklab
2025-05-07  1:47 ` dpdklab
2025-05-07  1:59 ` dpdklab
2025-05-07  2:25 ` |WARNING| " dpdklab
2025-05-07  2:45 ` dpdklab
2025-05-07  2:47 ` dpdklab
2025-05-07  2:49 ` dpdklab
2025-05-07  3:00 ` |SUCCESS| " dpdklab
2025-05-07  3:10 ` dpdklab
2025-05-07  3:12 ` dpdklab
2025-05-07  3:14 ` dpdklab
2025-05-07  3:14 ` dpdklab
2025-05-07  3:24 ` dpdklab
2025-05-07  3:26 ` dpdklab
2025-05-07  3:38 ` |WARNING| " dpdklab
2025-05-07  3:39 ` dpdklab
2025-05-07  3:39 ` dpdklab
2025-05-07  3:41 ` |SUCCESS| " dpdklab
2025-05-07  4:02 ` |WARNING| " dpdklab
2025-05-07  4:10 ` |FAILURE| " dpdklab
2025-05-07  4:18 ` dpdklab
2025-05-07  4:19 ` dpdklab
2025-05-07  4:23 ` dpdklab
2025-05-07  4:25 ` dpdklab
2025-05-07  4:28 ` dpdklab
2025-05-07  4:29 ` dpdklab
2025-05-07  4:31 ` dpdklab
2025-05-07  4:32 ` dpdklab
2025-05-07  4:33 ` dpdklab
2025-05-07  4:33 ` dpdklab
2025-05-07  4:36 ` |WARNING| " dpdklab
2025-05-07  4:37 ` dpdklab
2025-05-07  4:37 ` dpdklab
2025-05-07  4:38 ` dpdklab
2025-05-07  4:58 ` |FAILURE| " dpdklab
2025-05-07  5:29 ` dpdklab
2025-05-07  5:30 ` dpdklab
2025-05-07  5:30 ` dpdklab
2025-05-07  5:31 ` dpdklab
2025-05-07  5:33 ` dpdklab
2025-05-07  5:36 ` dpdklab
2025-05-07  5:40 ` dpdklab
2025-05-07  5:41 ` dpdklab
2025-05-07  5:42 ` dpdklab
2025-05-07  5:43 ` dpdklab
2025-05-07  5:44 ` dpdklab
2025-05-07  5:44 ` dpdklab
2025-05-07  5:44 ` dpdklab
2025-05-07  7:05 ` dpdklab
2025-05-07  7:13 ` dpdklab
2025-05-07 16:06 ` dpdklab
2025-05-07 16:10 ` dpdklab
2025-05-07 16:32 ` dpdklab
2025-05-07 16:37 ` dpdklab
2025-05-07 17:01 ` dpdklab
2025-05-07 17:06 ` dpdklab
2025-05-07 17:48 ` dpdklab [this message]
2025-05-07 18:36 ` |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=681b9cda.050a0220.279a78.a068SMTPIN_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).